maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Connolly (JIRA)" <>
Subject [jira] Closed: (MDEPLOY-75) uniqueVersion, includeAttachedArtifacts
Date Mon, 23 May 2011 10:54:22 GMT


Stephen Connolly closed MDEPLOY-75.

    Resolution: Won't Fix

A pom based project has which allows specification
of the uniqueVersion parameter in /project/distributionManagement/snapshotRepository

There is no need for the deploy goal of the maven-deploy-plugin to have this parameter.

The other feature you were looking for goes against the whole spirit of the lifecycle, but
if you still want it considered please raise it in a separate JIRA (keep one issue per JIRA)

> uniqueVersion, includeAttachedArtifacts
> ---------------------------------------
>                 Key: MDEPLOY-75
>                 URL:
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.3
>            Reporter: Francis Korning
>         Attachments:
> 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:
For more information on JIRA, see:


View raw message