Bug 5868 - Java Binding Project cannot reference a library project
Summary: Java Binding Project cannot reference a library project
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.2.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Atsushi Eno
URL:
Depends on:
Blocks:
 
Reported: 2012-06-26 13:21 UTC by tsukrov
Modified: 2012-07-03 03:50 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description tsukrov 2012-06-26 13:21:59 UTC
Something goes wrong and I cannot use my utility classes in Additions 
folder. 

https://dl.dropbox.com/u/57530319/TESTLIB.zip
Comment 1 Miguel de Icaza [MSFT] 2012-06-29 11:42:52 UTC
Could you describe on this bug what error do you get, or why you can not use the utility classes?
Comment 2 Atsushi Eno 2012-06-29 12:13:59 UTC
miguel: the problem is that the project somehow fails to add the references (that are added to the project) when it actually compiles the binding library.

We need to sort out how MSBuild task deals with that (jpobst used to work on it, now the rest of us need to do that).
Comment 3 Atsushi Eno 2012-07-02 08:17:31 UTC
This should be fixed, in 4.2.5 (we are already building 4.2.4 and this fix is done after that, sorry for that). Thanks for the report.
Comment 4 Atsushi Eno 2012-07-02 23:20:25 UTC
The fix in the current state turned out to be regressive, so I'll have to find out another way to fix issues. I'll close this bug again once I made it.
Comment 5 Atsushi Eno 2012-07-03 03:50:18 UTC
This is fixed (again, but does not regress like before ;-)