Thanks for confirming my findings, Emanuel! Sorry for not clarifying in my response that I had read the earlier thread.
I also read that "this" was fixed recently, which is why I'm asking for an update. Joe On Mar 16, 6:38 pm, Emanuel Moecklin <[email protected]> wrote: > On Wednesday, March 16, 2011 3:42:58 PM UTC-4, joebowbeer wrote: > > > In my tests with the latest tools, the custom attribute's namespace > > declaration in the library project needs to match the package > > declaration of the including project. Correct? > > It has to match the package declaration in AndroidManifest.xml otherwise the > layout will not compile. > If the package is the same as the including project then you are right but > library projects make sense if you have at least two including projects > (free and paid app e.g.) which will obviously have different package > declarations if you want to publish them on Android market. With two > including projects with different package declarations it's obviously not > possible to match both. > > > > > As far as I can tell, this is a known limitation and the suggested > > workaround is to copy the affected resources (e.g., main.xml in the > > example above) into each of the including projects. > > See Xavier's post from July 2010. Please read the whole thread before > repeating what others have written. > > Emanuel Moecklin -- 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
