On 01/03/2008, at 9:02 AM, Jason van Zyl wrote:
Here's the direction I would like to go in:
http://docs.codehaus.org/display/MAVEN/URL-based+dynamic+loading+of+providers+for+artifact+retrieval+and+deployment
Full support for all types of transport for retrieval and deployment
in a standard way that doesn't bloat out the core.
Yes, I'm generally in favour of the proposal - it is how we've always
wanted it to work.
Comments on the proposal:
- I don't see anything that allows strictly versioning the providers.
This may not be a concern as I don't know if that really impacts
reproducibility of the build, but there does need to be a way to pin
it down. How about an optional element in the deployment target
(currently <repository> under distMgmt):
<provider>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
<version>1.0</version>
</provider>
- +1 to move selected configuration into the distMgmt. However,
anything that might be overridden on a case-by-case basis (like
altDeploymentRepository) should not be in there
- I don't see any point of putting the deploy plugin version in there
- the standard mechanism is fine.
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
