New manifest merger: No enum constant com.android.manifmerger.AttributeOperationType.IGNORE

1,378 views
Skip to first unread message

Pierre-Luc Paour

unread,
May 15, 2014, 12:18:09 PM5/15/14
to adt...@googlegroups.com
I'm trying to use the new manifest merger with Gradle 1.11 and Android plugin 0.10.1, in order to use the new ${packageName} facility to support different search suggestions on my various app flavors.

The old merge system worked (merging two Manifest files), but the new one fails with the titular error. Apart from the package name injection, I'm not using any of the new merge features and my manifest files do not overlap, but contain completely separate elements (apart from the root manifest and the application singleton).

The stack trace of the build error can be seen here: https://gist.github.com/paour/b2a69bc46e9cb34f455c

Regretably, the log file doesn't contain any indication of the specific node that caused the problem…

Xavier Ducrohet

unread,
May 16, 2014, 2:34:08 PM5/16/14
to adt...@googlegroups.com


--
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+u...@googlegroups.com.
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!

Tomek Rozbicki

unread,
May 17, 2014, 9:31:58 AM5/17/14
to adt...@googlegroups.com
Just remove the tools:ignore="UnusedAttribute"
Reply all
Reply to author
Forward
0 new messages