On Thu, Aug 7, 2014 at 2:20 PM, William Ferguson < [email protected]> wrote: > > 1) Maven central is the first point of call when resolving dependencies. > So you will get the official artifacts ahead of the HE artifacts. >
This is not true. You can configure this behavior, but it's not Gradle's default. Moreover, HE isn't publishing these to Maven central because they do not have the rights to this groupId. > 2) Publishing in Maven central doesn't require manually downloading and > deployment of each version of the Android artifacts for each developer. > They become instantly available as soon as they are published by the > Android team. So you remove attack via update latency. > This makes no sense to me. > 3) Publishing the Android artifacts in central marks ownership of the > namespace. It is less likely for someone to attempt to usurp that namespace > elsewhere as users can see that the namespace is owned and being used. Ie > its territory communication. > Both com.google.* and com.android.* are already widely used groupIds by Google for thousands of artifacts in central so this doesn't change anything. What you are seeing is an old, legacy Maven project doing ugly hacks to try and make things work. It affects neither Gradle nor Ant builds which are the only supported mechanisms of building Android apps. -- 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.
