You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Francis Korning (JIRA)" <ji...@codehaus.org> on 2008/03/28 16:45:58 UTC
[jira] Updated: (MDEPLOY-75) uniqueVersion,
includeAttachedArtifacts
[ http://jira.codehaus.org/browse/MDEPLOY-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis Korning updated MDEPLOY-75:
-----------------------------------
Attachment: MDEPLOY-75-patch.zip
> uniqueVersion, includeAttachedArtifacts
> ---------------------------------------
>
> Key: MDEPLOY-75
> URL: http://jira.codehaus.org/browse/MDEPLOY-75
> Project: Maven 2.x Deploy Plugin
> Issue Type: New Feature
> Affects Versions: 2.3
> Reporter: Francis Korning
> Attachments: MDEPLOY-75-patch.zip
>
>
> by default the maven deploy plugin is inconsistent in its use of the uniqueVersion flag, which can be set manually in the explicit deploy-file goal but isn't present in the implicit deploy goal.
> another thing we'd like to do is disabling the deployment of deliverable attached artifacts, or allowing to select only specific artifacts, classifiers, or assemblies. for deployment.
> new configuration parameters include:
> || parameter || type || default || description ||
> | uniqueVersion | boolean | true | use uniqueVersion buildnumbers (${artifactId}-YYYYmmdd-HHmmss-nn) |
> | includeAttachedArtifacts | boolean | true | also deploy attached artifacts |
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira