if you don't have that many modules it shouldn't be too hard. Just find modules where the package name defined in the manifest is a dup of the one used by another module.
On Wed, Mar 26, 2014 at 11:09 AM, Scott Battaglia <[email protected] > wrote: > Thanks, I've voted :-) > > Any recommendations for what to do in the meantime? For now, I've put > upgrading aside as I don't want to set the flag to false. > > > On Wed, Mar 26, 2014 at 2:06 PM, Xavier Ducrohet <[email protected]> wrote: > >> hmm yeah we don't really tell you what the package name is or where the >> conflict is. We should improve this. >> >> https://code.google.com/p/android/issues/detail?id=67691 >> >> >> On Wed, Mar 26, 2014 at 10:59 AM, Scott Battaglia < >> [email protected]> wrote: >> >>> I'm attempting to upgrade to 0.9.1 and I'm getting this error: >>> >>> 13:34:58.298 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build >>> failed with an exception. >>> 13:34:58.298 [ERROR] [org.gradle.BuildExceptionReporter] >>> 13:34:58.299 [ERROR] [org.gradle.BuildExceptionReporter] * What went >>> wrong: >>> 13:34:58.299 [ERROR] [org.gradle.BuildExceptionReporter] Execution >>> failed for task ':lib1:processDebugTestResources'. >>> 13:34:58.299 [ERROR] [org.gradle.BuildExceptionReporter] > Error: A >>> library uses the same package as this project >>> 13:34:58.300 [ERROR] [org.gradle.BuildExceptionReporter] You can >>> temporarily disable this error with android.enforceUniquePackageName=false >>> 13:34:58.300 [ERROR] [org.gradle.BuildExceptionReporter] However, this >>> is temporary and will be enforced in 1.0 >>> >>> I'm attempting to resolve it rather than set the flag to false but the >>> build is not returning any useful information for me to hunt it down (at >>> least that I can find). I run the build with "--debug" and I'm not seeing >>> any additional useful information. I've also manually inspected the values >>> in each AndroidManifest.xml and everything look unique. >>> >>> Is there a way for this error to produce more useful information for >>> tracking down/fixing especially if in 1.0 this is gong to be enforced? Or >>> is there a specific place I should be looking to find out what the conflict >>> is? >>> >>> Thanks >>> Scott >>> >>> -- >>> 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. >> > > -- > 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.
