Wow... you guys got a bit of a debate going here ;-) I just wanted to clarify and mention a few things:
1. I am happy that the SDK team pushes sdklib and others to the Central Repo. 2. I am happy that they include the proprietary and other components in the SDK in the form of a Maven repo. The Android Maven Plugin, my Maven Android SDK Deployer just like many of Jakes and other projects are community efforts. Google and the Android team should imho support them where they can with the limited resources they have. They always have been and still are a imho small team of excellent people with very limited resources. Now with regards to the coordinate usage and the such. 1. Yes.. it would be better if google would publish all components in a repository somewhere. Central would be good, but their own Maven repo or so would be just as good. Publishing them via the SDK is a compromise .. ideally it would at least include all the components including the android jar itself. This would give them a leadership position on what the coordinates should be and reduce confusion for users by simply setting a standard. 2. The Maven Android SDK deployer can publish the repo other artifacts into a repository manager and therefore makes it all available. I had numerous requests from various cloud CI server platform providers and other development infrastructure providers to use it to publish the artifacts and I had to advise against them due to the legal concerns with the EULA. Even Google itself does not publish in a repo without the SDK EUAL click through. There definitely is a need in the community for a repo .. Google just chooses to prioritize it low/ignore it (for now?) forcing workarounds. Same applies to e.g. the Eclipse support at the moment. 3. The Android Maven plugin could provision the plugins into a repository/repo manager but the Maven Android SDK Deployer already does that. It has to be provisioned into a repo since other plugins also have to be able to access these dependencies. If it is a really easy fix I still always welcome your pull request Jake or anyone else's as well. Overall I think that there is no really big problem here. Yes.. it would be better if Google would take more of a leadership role and participate more in the community even by simple things like setting standards and making recommendations. And yes... I am still hoping for more good things to come from Google and the SDK team and I am sure there will be.. And yes... the SDK team is small and they have a lot on their plate and the community steps up and does their thing. And no... telling people not to use their tool of choice and is not good taste and not necessary. There are many happy Android Maven Plugin users or Eclipse users and they contribute to the Android eco system just like the in-crowd of Gradle and IntelliJ users do. I have been using Intellij since version 4.x and happily switch to Eclipse and back all the time. Both are great tools with their strengths and weaknesses just like Maven and Gradle. And there are lots of others around that all deserve to be helped and embraced. Choice is good. Lets all work together even more and we can make things even better.. Manfred PS: Every company uses lots of competing tools. In fact I am sure Google and Square both use Gradle and Maven heavily.. so what? Both are better than make ... hahaha -- 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.
