On Jan 26, 2:33 pm, Mark Murphy <[email protected]> wrote: > True, though I'm a bit hesitant to rely upon that behavior until they > release the full library-project-as-distributable-JAR support.
Why is this? You're basically just depending on the R symbols being defined in a class that's not in the library jar file but instead is elsewhere in the classpath of the VM. Typical shared library stuff. The host project will create and include that R class from the resources that are in your library project and everything is good. The user of your lib just can't be messing with the names of the resource files -- then there will be a problem. Granted, it would be much better if Google created a full library-as- JAR solution, making AAPT smart enough to grab resources out a jar instead of looking for them in the filesystem. But this should work as long as nothing is meddled with. Doug -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
