Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.3
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
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 |
A pom based project has http://maven.apache.org/pom.html#Repository 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)