You shouldn't change the applicationId for a library. The idea of customizing applicationId for an app is about creating an app with a different ID than the package defined in src/main/AM.xml in order to change the ID without refactoring all the code that import that app's R class.
For library, though the mechanism relies on the library package (as defined in the src/main/AM.xml file) and the R class to be in the same package. I'm not sure if we do enforce this or not at the moment, so I just filed https://code.google.com/p/android/issues/detail?id=77250 to track this. On Wed, Oct 8, 2014 at 1:21 AM, Roman Mazur <[email protected]> wrote: > Recent changes of the gradle plugin replaced packageName with > applicationId. > And this article > http://tools.android.com/tech-docs/new-build-system/applicationid-vs-packagename > explains the reasons. > > However, I wonder why library plugin has API to set application id. They > seem to have package name only. > I actually even do not know whether applicationId is required when > 'com.android.library' is applied. Is it? > > Please let me know if I miss smth about how applicationId is used for > libraries. > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
