Someone reported this to me a few weeks ago already, but I didn't have time to look into it.
I just email the Gradle dev list asking for their opinion on this, since it's Gradle itself that's generating the POM (our plugin doesn't do anything). On Tue, Aug 5, 2014 at 1:23 PM, Tomáš Procházka <[email protected]> wrote: > I have one gradle related question. > > This project > https://github.com/ManuelPeinado/FadingActionBar > has one aar module that depend on another one and on app compat library. > But during deploying to the maven repository, gradle don't generate > <scope>aar</scope> to the dependency declaration. > So by maven definition it mean that dependency should be .jar not .aar. > It is bug of gradle itself or bug in your android plugin which define aar? > > Problem is described also here: > https://github.com/ManuelPeinado/FadingActionBar/issues/70 > > -- > 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. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
