Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
It is not uncommon for a .jar to contain additional .jar files which are dependencies. Consider the mythical MyLib.jar contents:
A normal binding of MyLib.jar will fail, because mylib.SomeType requires a type from dependency.jar, and dependency.jar isn't a ReferenceJar.
The current workaround is to unzip MyLib.jar and add lib/dependency.jar as a ReferenceJar, which will allow MyLib.jar to be bound.
What could instead happen is that MyLib.jar is searched for all .jar & .html files. Embedded .jar files would be extracted and implicitly used as ReferenceJars, while .html files could be used for doc import (if/when we get doc import working...).
Let's consider this sort of jars which look "unusual" later, once it is found not so unusual. (hence leaving as enhancement as is)
@Atsushi, any update?
Quite old report with old ideas.
This should not be handled by the target jar library itself.
Any referenced libraries should be in DLL form, where the DLL itself should contain any documented parameter names for the exact reference library.