maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Vorburger (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MDEPLOY-211) uniqueVersion broken (if not supported, should be removed from doc, and warning printed)
Date Sat, 18 Jun 2016 17:15:05 GMT
Michael Vorburger created MDEPLOY-211:
-----------------------------------------

             Summary: uniqueVersion broken (if not supported, should be removed from doc,
and warning printed)
                 Key: MDEPLOY-211
                 URL: https://issues.apache.org/jira/browse/MDEPLOY-211
             Project: Maven Deploy Plugin
          Issue Type: Bug
          Components: deploy:deploy-file
            Reporter: Michael Vorburger


Doc on 1. http://maven.apache.org/plugins/maven-deploy-plugin/usage.html as well as 2. http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
as well as 3. http://maven.apache.org/plugins/maven-deploy-plugin/file-deployment.html (link
"Disable timestamps suffix in an artifact", currently broken!) currently mentions a uniqueVersion.

This appears to be broken at least with Maven v3.3.9. For example, if I do:

{noformat}$ mvn deploy:deploy-file -Durl=file:///tmp/system -DrepositoryId=some.id -Dfile=target/hello-impl-0.1.0-SNAPSHOT.jar
-DpomFile=pom.xml -DuniqueVersion=false
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building hello-impl 0.1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.2:deploy-file (default-cli) @ hello-impl ---
Downloading: file:///tmp/system/org/opendaylight/vorburger/hello/hello-impl/0.1.0-SNAPSHOT/maven-metadata.xml
Uploading: file:///tmp/system/org/opendaylight/vorburger/hello/hello-impl/0.1.0-SNAPSHOT/hello-impl-0.1.0-20160618.170929-1.jar
{noformat}

Note hello-impl-0.1.0-20160618.170929-1.jar despite -DuniqueVersion=false.

If this possibility has been removed, as I have the feeling it has been from posts incl. MDEPLOY-44
(that was about adding uniqueVersion to deploy just like, supposedly, it is on deploy-file;
this is about it not even working on deploy-file, anymore), then before you close this as
WONTFIX, I would argue this current half removal is confusing to say the least ..

If this is not coming back, then the uniqueVersion configuration should be fully removed from
maven-deploy-plugin, and the documentation in at least 3 places referred to above should be
cleaned up accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message