Jake you appear to be looking at the world through a very blinkered view. All of what you said works perfectly in a homogenized world, but the world is not that way.
There are many forces dictating build environments, not all them within an individual developer's control. And even when the individual does have control there are economic considerations. My point is that because their artifacts are published to a publicly >> accessible web address their artifacts are more accessible than those being >> provided by the Android team. >> > > But not Maven central, therefore not a problem. > Gradle: If you are using a shared (eg corporate) repo then you are at risk. Ant: If you are using dep management then you are at risk. > A) Before you can consume any of the artefacts you need to start SDK >> manager, choose the appropriate versions of the required artifacts and then >> download them. >> > > Every developer does this. You need the API level you are compiling > against. This isn't a problem > API level is an orthogonal issue. This is about whether the dependencies that you download are the dependencies that you expect. You seem to be missing the point that these deps can be drawn in transitively without your knowledge, for Gradle and Ant as well as Maven. I'm aware of your history with the android-maven-plugin. It is 3rd party and open source, no reason it can't also be adopted or at the very least not shut out. It was painful largely because we had to constantly fight with the Android build tools. Now that those tools are being published as Maven artifacts there is less fight and more co-operation. A lot of us feel that Gradle is where Maven1 was at in 2003. A great concept but far from usable. I recently tried to drag a group of developers who were used to Ant and Maven across to Gradle and after 4 weeks trying to chow down we ended up converting the whole lot to Maven3. > > Most developers don't use the SDK Manager to download the latest artifacts >> on a daily basis, they do it at irregular intervals. This means that there >> is a latency between when the artifacts become available and when the >> developer first has access to the official artifacts. >> > > I agree. I wrote a Gradle plugin to address this: > https://github.com/JakeWharton/sdk-manager-plugin. I'd love for the > first-party plugin to do this some day. > > Right so it's problem. And you have a Gradle work around. I'm suggesting we fix the problem. -- 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.
