On 20/11/2012, at 8:40 AM, Luke Daley wrote:
> Hi,
>
> At the moment, we have one construct for defining maven repositories to
> consume dependencies from (i.e. maven { url … }) and an entirely different
> one for deploying (i.e. mavenDeployer { }). The strategy with the new
> publication mechanism is to try and have one construct.
>
> Where would the equivalent of addProtocolProviderJars() fit into this?
It doesn't. It exposes the fact that wagon is being used under the covers, and
we don't want to do this, because we want the option to change how we publish
to a Maven repo. Instead, Gradle should ship with the jars that are required to
publish to file and http URLs. And later we'll add support for sftp and webdav,
before we deprecate the old maven publish stuff.
--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com
