Actually this is Gradle violating Maven standards. The packaging type in maven only applies to that artifact, not any dependencies. If a type is not specified on a dependency in a pom, maven assumes that it is JAR. Gradle is breaking compatibility with other tooling in this particular case.
More info here: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html Particularly in the examples. If type is not specified, maven assumes jar. On Thursday, August 7, 2014 at 11:51:41 AM UTC-4, Jake Wharton wrote: > > On Thu, Aug 7, 2014 at 5:23 AM, Tomáš Procházka <[email protected] > <javascript:>> wrote: > >> >> 2014-08-07 13:20 GMT+02:00 William Ferguson <[email protected] >> <javascript:>>: >> >> This is bad. Similar to Gradle versions of "+" being copied into Maven >>> poms. >>> If it is a Gradle Android plugin doing this then the plugin needs to be >>> fixed. >>> >> >> So you think that this is issue of Gradle Android plugin not gradle >> itself? >> > > It isn't. I can do this in any Gradle project, Android or not. This is > user education issue that is not at all specific to Android. > > > -- 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.
