Wrong .. the Android Maven Plugin is fully capable of creating aar files as well as consuming them as a dependency (or transitive dependency). Problem is that the pom created by Gradle does not specify the dependencies correctly.
Manfred Robert Patrick wrote on 08.12.2014 08:40: > The problem is almost certainly because the code below specifies a packaging > type of “aar” without the requisite work to teach Maven about that > packaging type (see > http://books.sonatype.com/mvnref-book/reference/writing-plugins-sect-plugins-lifecycle.html)? > > > > > > I see no reason to eliminate the assumption that any dependency without a > known > packaging type specified is a jar. > > > > > > -- > > Robert Patrick <HYPERLINK > "mailto:robert.patr...@oracle.com"robert.patr...@oracle.com> > > VP, FMW Platform Engineering, Oracle Corporation > > 7460 Warren Pkwy, Ste. 300 Office: +1.972.963.2872 > > Frisco, TX 75034, USA Mobile: > +1.469.556.9450 > > > > HYPERLINK > "http://www.amazon.com/Professional-Oracle-WebLogic-Server-Patrick/dp/0470484306/"Professional > Oracle WebLogic Server > > by Robert Patrick, Gregory Nyberg, and Philip Aston > > with Josh Bregman and Paul Done > > Book Home Page: HYPERLINK > "http://www.wrox.com/WileyCDA/WroxTitle/Professional-Oracle-WebLogic-Server.productCd-0470484306.html"http://www.wrox.com/ > > Kindle Version: HYPERLINK > "http://www.amazon.com/Professional-Oracle-WebLogic-Server-ebook/dp/B004HD69J2/"http://www.amazon.com/ > > > > > > From: William Ferguson [mailto:william.fergu...@xandar.com.au] > Sent: Sunday, December 07, 2014 6:25 PM > To: maven-android-develop...@googlegroups.com > Cc: Maven Developers List > Subject: Re: problem with AAR dependency > > > > ## Cross posting to Maven Dev list > > > > One solution to this would be to change the POM specification to require the > type element for dependencies. > > That would allow Maven and MavenCentral to immediately fail POMs based upon > dependencies that are missing the type element. > > > > Yes, it goes against convention over configuration, but Maven is now used by > many more build types than just plain Java builds so maybe we need to consider > that the convention is no longer to assume jar dependencies. > > > > I would rather require a little more configuration to ensure that builds are > more deterministic. > > If we want to shrink the size of the POM then the new POM format is a better > solution. > > > > William > > > > On Thursday, December 4, 2014 1:47:33 AM UTC+10, Andreas Schildbach wrote: > > I'm using maven-android-plugin 4.0.0 with Maven 3.0.5. I've got troubles > declaring an aar dependency. Here is the pom.xml declaration: > > <dependency> > <groupId>com.android.support</groupId> > <artifactId>support-v13</artifactId> > <version>21.0.2</version> > <type>aar</type> > </dependency> > > > Just about any Maven command, even "mvn dependency:tree" yields: > > [ERROR] Failed to execute goal on project wallet: Could not resolve > dependencies for project de.schildbach.wallet:wallet:apk:4.13-test: Failure to > find com.android.support:support-v4:jar:21.0.2 in HYPERLINK > "file:///\\home\aschildbach\dev\android-sdk\extras\android\m2repository"file:///home/aschildbach/dev/android-sdk/extras/android/m2repository > was cached in the local repository, resolution will not be reattempted until > the update interval of android-support has elapsed or updates are forced -> > [Help 1] > > Where does that .jar type in the error message stem from? I declared aar. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
