I am using Build Tools v. 21.1.1 and it doesn't work for me.
-build-setup:
[getbuildtools] Using latest Build Tools: 21.1.1
[echo] Resolving Build Target for android-domain...
[gettarget] Project Target: Android 5.0.1
[gettarget] API level: 21
...
-code-gen:
[mergemanifest] Merging AndroidManifest files into one.
[mergemanifest] Manifest merger disabled. Using project manifest only.
[echo] Handling aidl files...
[aidl] No AIDL files to compile.
[echo] ----------
[echo] Handling RenderScript files...
[echo] ----------
[echo] Handling Resources...
[aapt] Generating resource IDs...
[echo] ----------
[echo] Handling BuildConfig class...
[buildconfig] Generating BuildConfig class.
I have tried "manifestmerger.enabled=true" in both project.properties and
build.properties. It doesn't seem to affect anything.
PS I run "ant clean", "ant debug' form the terminal. MacOS.
On Friday, June 8, 2012 5:00:08 PM UTC-7, Xavier Ducrohet wrote:
>
> Can you double check that the prop name is "manifestmerger.enabled" ?
>
> On Tue, Jun 5, 2012 at 7:20 PM, Scott Kennedy <skenn...@gmail.com
> <javascript:>> wrote:
> > What's the status of this now? It was listed in the release notes for
> r20
> > preview 3, but when I try to use it in ant, it always gives me:
> > Merging AndroidManifest files into one.
> > Manifest merger disabled. Using project manifest only.
> >
> > That's with the property set to true in my build.xml, or in
> > project.properties. I have no idea how to get it going in Eclipse with
> ADT.
> >
> > I'd love to help test this so that the bugs are gone by the time it's
> > released, but I'm having trouble right now =(
> >
> > Thanks
> >
> > On Monday, May 21, 2012 7:09:44 PM UTC-4, Joe Bowbeer wrote:
> >>
> >> Good to know. Thanks.
> >>
> >> Based on the ManifestMerger.java source reviewed below, I can't figure
> out
> >> how meta-data is handled. Can library manifests add meta-data to
> components
> >> defined in the main manifest, or vice versa?
> >>
> >> I'm planning to leverage manifest merging, but I haven't finalized a
> >> strategy yet. At first glance, meta-data looks like it could be a
> useful
> >> site for customization, but maybe not.
> >>
> >> https://android-review.googlesource.com/#/c/36692/
> >>
> >>
> >> On Mon, May 21, 2012 at 10:33 AM, Tor Norbye wrote:
> >>>
> >>> Yeah, it's in progress; ant should be checked in, I think Xav is
> >>> working on ADT integration.
> >>> https://android-review.googlesource.com/#/c/35472/
> >>> (the merger itself is in changeset
> >>> 2ccd27ce4e32da8832d2810f152b1752074bfd41 )
> >>>
> >>> -- Tor
> >>>
> >>> On Mon, May 21, 2012 at 10:31 AM, Joe Bowbeer wrote:
> >>> > Has there been any progress in merging the main+library manifests in
> a
> >>> > build? Or a description of the functionality that is planned?
> >>> >
> >>> > If any of the Android Tools previews even partially accomplish this,
> I
> >>> > would
> >>> > like to check it out.
> >>> >
> >>
> >>
> >
>
>
>
> --
> 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 adt-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
