Hello,
This is expected; the solution for you is, move "bin/res" directory as
top-level "res".
Background: the existing Android Library Project support in Jar Binding
project needed structural changes in the files layout.
We found that "bin/res" directory does not contain sufficient files that
needs to be packaged, and it should be rather "res" (top-level)
directory instead.
Hence, since 4.2.5, when there is LibraryProjectProperties, MfA collects
resources from top-level "res" directory. Your project has fell into
some "unexpected" structure that there is only "bin/res" directory,
which used to be inspected but now it *isn't*. And the new MfA behavior
should be correct.
If you have LibraryProjectProperties in your "true" (in other words
"expected") android library project, this should not happen because you
are supposed to have "res" directory as expected.
I believe you had that directory structure only for creating binding
project from some isolated place. So it shouldn't bite in your real
hacking life.
For the directory changes, we have described that in our release note:
http://docs.xamarin.com/android/Releases/Mono_For_Android_4/Mono_for_Android_4.2.5#Changes_needed_to_Android_Library_project_support_in_Java_binding_project
Atsushi Eno
tsukrov wrote:
https://dl.dropbox.com/u/57530319/AndroidApplication1.zip
The project to reproduce the issue.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/4-2-5-resources-party-stopper-tp5711078p5711082.html
Sent from the Mono for Android mailing list archive at Nabble.com.
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid