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?
Options:
1. MavenArtifactRepository
2. PublishToMavenRepository (task)
#1 is the obvious choice, but we would then be introducing configuration
options only valid for publishing.
#2 could be more appropriate, because you could think of this as a function of
the publish operation and not necessarily the destination. That's a dicey call
though.
--
Luke Daley
Principal Engineer, Gradleware
http://gradleware.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
