You were complaining about non-standard artifacts. It solves it by always using official artifacts.
I don't care that there's slightly higher overhead for Maven users (which the continued fact that it's wholly unsupported falls on your deaf ears). That's the price you pay for doing the right thing. On Thu, Aug 7, 2014 at 6:52 PM, William Ferguson < [email protected]> wrote: > On Fri, Aug 8, 2014 at 10:43 AM, Jake Wharton <[email protected]> > wrote: > >> Your problem is one for the Maven community. >> >> Get them to fix it by delegating to the SDK for the API jar and the two >> embedded m2 repos. ~50 line change in the plugin, problem completely solved. >> >> > This does *NOT* solve the issue. This does not even reference the issue. > > I can't believe believe that someone like yourself can pretend to be so > wilfully ignorant of the impact of the spread of GAV equivalent artifacts > that have a higher visibility that those produced by the Android team. > > William > > -- > 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. > -- 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.
