You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/08/22 10:44:32 UTC
[jira] Commented: (MDEPLOY-121) Allow uniqueVersion as
deploy:deploy parameter or altDeploymentRepository field
[ https://jira.codehaus.org/browse/MDEPLOY-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276641#comment-276641 ]
Stephen Connolly commented on MDEPLOY-121:
------------------------------------------
Given that Maven 3 does not support uniqueVersion=false I do not see the value in adding this support.
Campaign for Maven 3 to support uniqueVersion=false and this issue becomes relevant again.
> Allow uniqueVersion as deploy:deploy parameter or altDeploymentRepository field
> -------------------------------------------------------------------------------
>
> Key: MDEPLOY-121
> URL: https://jira.codehaus.org/browse/MDEPLOY-121
> Project: Maven 2.x Deploy Plugin
> Issue Type: New Feature
> Components: deploy:deploy
> Affects Versions: 2.5
> Reporter: SebbASF
> Assignee: Mark Struberg
> Labels: scrub-review-started
> Attachments: deploy.patch, deploy.patch
>
>
> The altDeploymentRepository property allows the id, layout and URL of a repository to be overriden.
> However it does not allow the uniqueVersion setting to be overriden.
> This reduces its usefulness as an override mechanism.
> Patch implements the feature by using one of the spare fields in the property:
> id::layout:uniqueVersion:url
> e.g.
> id::layout:true:url
> id::layout:false:url
> id::layout::url
> If the value is empty, it defaults to true, as per the previous behaviour.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira