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.
According to the release notes, since MfA 4.4 one should be able to use a Java Bindings Library project without referencing the jar file from the bindings project (build action: "AndroidJavaLibrary").
However, in my particular case it doesn't work. Here's the output I get when building my project:
where "MAInterface" is the "Java Bindings Library" and "NaviOutput" is the main project.
Note that the project compiles fine when I reference the jar file as "AndroidJavaLibrary".
Does your *.jar library file in the binding project have "EmbeddedJar" build action? Our new jar embedding feature does NOT mean existing binding project always embeds the jars (or we will break everyone's existing apps). As long as the existing binding has InputJar build action, you still need to also provide AndroidJavaLibrary to applications.
I'm guessing my comment exactly explains the situation, so closing the bug as feature. If that was not the case please reopen and give more details.