Ok I have a fix which I am about to send for review.
In the meantime, if I am not mistaken you have package definitions in your
build-type specific Android Manifests (with the same value as in the main
manifest file), correct ? if so, remove all the build-type and flavors
package definitions, leave the main manifest package definition of course.
Use the build.gradle applicationIdSuffix to specialize your package per
build type.
Thanks for your patience.
Jerome
On Fri, Jun 27, 2014 at 12:43 AM, Mateusz Grzechociński <
mateusz.grzechocin...@gmail.com> wrote:
> W dniu piątek, 27 czerwca 2014 03:00:09 UTC+2 użytkownik Jerome Dochez
> napisał:
>
> some more information, another way you can customize your debug
>> application Id is by following these steps :
>>
>> 1. in your build.gradle
>> debug {
>> applicationIdSuffix 'debug'
>> }
>>
>> 2. in your main manifest file, leave your package declaration but remove
>> it from all the build-type/flavor specific AndroidManifest files.
>>
>> this is not generating the issue you mentioned above.
>>
>
> I already modify applicationIdSuffix in my debug buildType. I followed
> your instructions (see below diff) but still:
>
> :app:processArmMoDebugManifest
> /Users/mateuszgrzechocinski/dev/myProject/app/src/debug/AndroidManifest.xml:2:1
> Error:
> Attribute manifest@package value=(com.myproject) from
> AndroidManifest.xml:3:11
> is also present at com.android.support:appcompat-v7:19.1.0:17:11
> value=(android.support.v7.appcompat)
> Suggestion: add 'tools:replace="package"' to <manifest> element at
> AndroidManifest.xml:2:1 to override
> :app:processArmMoDebugManifest FAILED
>
> Here is my full diff:
>
> 09:35:29] in ~/d/p/i/android(2.X|ae08ba5|✚3)
>
>
>
> ↪ git diff
> diff --git a/app/src/debug/AndroidManifest.xml
> b/app/src/debug/AndroidManifest.xml
> index 71d937a..249ff8d 100644
> --- a/app/src/debug/AndroidManifest.xml
> +++ b/app/src/debug/AndroidManifest.xml
> @@ -1,8 +1,8 @@
> <?xml version="1.0" encoding="utf-8"?>
> -<manifest xmlns:android="http://schemas.android.com/apk/res/android";
> - package="com.myproject">
> +<manifest xmlns:android="http://schemas.android.com/apk/res/android";>
>
> - <application>
> - <activity android:name=".devopts.DevOptionsActivity"
> android:screenOrientation="portrait"/>
> +
> +<application>
> + <activity android:name="com.myproject.devopts.DevOptionsActivity"
> android:screenOrientation="portrait"/>
> </application>
> </manifest>
> diff --git a/build.gradle b/build.gradle
> index 4fd53f3..150ffec 100644
> --- a/build.gradle
> +++ b/build.gradle
> @@ -3,7 +3,7 @@ buildscript {
> mavenCentral()
> }
> dependencies {
> - classpath 'com.android.tools.build:gradle:0.11.+'
> + classpath 'com.android.tools.build:gradle:0.12.+'
> classpath 'org.ajoberstar:gradle-git:0.8.0'
> }
> }
>
> Thanks in advance for fixing this issue.
>
> M.
>
>
>
>>
>> On Thu, Jun 26, 2014 at 5:25 PM, Jerome Dochez <je...@google.com> wrote:
>>
>>> first, if you are stuck you can always revert to the old manifest merger
>>>
>>> android {
>>> *useOldManifestMerger true*
>>> }
>>> now, we should not be merging the manifest attributes coming from
>>> libraries. This is obviously a bug we need to fix on our end.
>>>
>>
> Yep, I know about that, but it's not so easy just to turn it off since I'm
> using new merger features like ${packageName{, which BTW seems to change to
> ${applicationId}
>
>
>
> --
> 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 adt-dev+unsubscr...@googlegroups.com.
> 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 adt-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
