A library package can only have the package name declared in its manifest. It's a limitation due to how the R class of the library is not packaged in its classes.jar and instead created by the consuming app.
Since the consuming app uses the library's manifest's package to generate the R class there's no way in the library to have a different package name for different variants (since in an app project, all variants use the original manifest package name for the R class and overrides the package name only in the packaged manifest) If you need to provide different libraries with different packages, you should use different modules. On Wed, Dec 3, 2014 at 7:05 PM, Kevin Kovach <[email protected]> wrote: > I see in the release notes for version 1.0.0-rc1 of the gradle plugin that > "Setting applicationId(Suffix) in a Library project will now properly > fail.", but I do not see anything indicating an alternative. How are we > supposed to be setting the package name in library projects? Thanks. > > - Kevin > > -- > 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.
