On 06/12/2012, at 9:36 AM, Steve Ebersole wrote: > I grey what you are saying and agree for the most part. Except for the "in > the gradle world" part. I think that to a degree once you apply the maven > plugin you are saying something about how you want certain things to work. > > The use case I am most thinking of is that of mixed build tool environments. > Yes forcing publishing to just the remote repo and then the maven build to > grab it from there works. But again it's a question of what is a reasonable > expectation from someone who has a gradle build with the maven plugin applied. >
We're talking here about the new 'maven-publish' plugin, not the 'maven' plugin. The idea is that the 'maven-publish' plugin is interested only in 'maven-the-repository-format' not 'maven-the-build-tool', and so is responsible only for taking artefacts and shoving them into one or more Maven repositories. For this plugin, we don't want to have publishing to a remote repository imply publishing to the local Maven cache. It certainly should be possible to configure Gradle to do this, but not the default. It's a separate question of what the 'maven' plugin does. That may well continue to do an implicit local publish on remote publish. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
