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 11:18:32 UTC

[jira] Commented: (MDEPLOY-138) can't upload existing jar+pom as one snapshot artifact

    [ https://jira.codehaus.org/browse/MDEPLOY-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276653#comment-276653 ] 

Stephen Connolly commented on MDEPLOY-138:
------------------------------------------

[stephenc@stephenc ~]$ rm -rf tmp
[stephenc@stephenc ~]$ usemvn 2.2.1
[stephenc@stephenc ~]$ mvn org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy-file -Dfile=mdeploy-134-poc.jar -DpomFile=pom.xml -DgeneratePom=false -Durl=file:./tmp/
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - localdomain.localhost:mdeploy-138-poc:jar:0.1-SNAPSHOT
[INFO]    task-segment: [org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy-file] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [deploy:deploy-file {execution: default-cli}]
[INFO] Retrieving previous build number from remote-repository
[INFO] repository metadata for: 'snapshot localdomain.localhost:mdeploy-138-poc:0.1-SNAPSHOT' could not be found on repository: remote-repository, so will be created
Uploading: file:./tmp//localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091442-1.jar
141K uploaded  (mdeploy-138-poc-0.1-20110822.091442-1.jar)
[INFO] Retrieving previous metadata from remote-repository
[INFO] repository metadata for: 'snapshot localdomain.localhost:mdeploy-138-poc:0.1-SNAPSHOT' could not be found on repository: remote-repository, so will be created
[INFO] Uploading repository metadata for: 'snapshot localdomain.localhost:mdeploy-138-poc:0.1-SNAPSHOT'
[INFO] Retrieving previous metadata from remote-repository
[INFO] repository metadata for: 'artifact localdomain.localhost:mdeploy-138-poc' could not be found on repository: remote-repository, so will be created
[INFO] Uploading repository metadata for: 'artifact localdomain.localhost:mdeploy-138-poc'
[INFO] Uploading project information for mdeploy-138-poc 0.1-20110822.091442-1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Mon Aug 22 10:14:42 IST 2011
[INFO] Final Memory: 4M/81M
[INFO] ------------------------------------------------------------------------
[stephenc@stephenc ~]$ find tmp
tmp
tmp/localdomain
tmp/localdomain/localhost
tmp/localdomain/localhost/mdeploy-138-poc
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/maven-metadata.xml
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/maven-metadata.xml.md5
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/maven-metadata.xml.sha1
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091442-1.jar
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091442-1.jar.md5
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091442-1.jar.sha1
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091442-1.pom
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091442-1.pom.md5
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091442-1.pom.sha1
tmp/localdomain/localhost/mdeploy-138-poc/maven-metadata.xml
tmp/localdomain/localhost/mdeploy-138-poc/maven-metadata.xml.md5
tmp/localdomain/localhost/mdeploy-138-poc/maven-metadata.xml.sha1

[stephenc@stephenc ~]$ rm -rf tmp
[stephenc@stephenc ~]$ usemvn 3.0.3
[stephenc@stephenc ~]$ mvn org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy-file -Dfile=mdeploy-134-poc.jar -DpomFile=pom.xml -DgeneratePom=false -Durl=file:./tmp/
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building mdeploy-138-poc 0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-deploy-plugin:2.6:deploy-file (default-cli) @ mdeploy-138-poc ---
Downloading: file:./tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/maven-metadata.xml
Uploading: file:./tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.jar
Uploaded: file:./tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.jar (142 KB at 5656.9 KB/sec)
Uploading: file:./tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.pom
Uploaded: file:./tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.pom (512 B at 250.0 KB/sec)
Downloading: file:./tmp/localdomain/localhost/mdeploy-138-poc/maven-metadata.xml
Uploading: file:./tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/maven-metadata.xml
Uploaded: file:./tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/maven-metadata.xml (780 B at 761.7 KB/sec)
Uploading: file:./tmp/localdomain/localhost/mdeploy-138-poc/maven-metadata.xml
Uploaded: file:./tmp/localdomain/localhost/mdeploy-138-poc/maven-metadata.xml (294 B at 287.1 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.496s
[INFO] Finished at: Mon Aug 22 10:15:21 IST 2011
[INFO] Final Memory: 3M/81M
[INFO] ------------------------------------------------------------------------
[stephenc@stephenc ~]$ find tmp
tmp
tmp/localdomain
tmp/localdomain/localhost
tmp/localdomain/localhost/mdeploy-138-poc
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/maven-metadata.xml
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/maven-metadata.xml.md5
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/maven-metadata.xml.sha1
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.jar
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.jar.md5
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.jar.sha1
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.pom
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.pom.md5
tmp/localdomain/localhost/mdeploy-138-poc/0.1-SNAPSHOT/mdeploy-138-poc-0.1-20110822.091520-1.pom.sha1
tmp/localdomain/localhost/mdeploy-138-poc/maven-metadata.xml
tmp/localdomain/localhost/mdeploy-138-poc/maven-metadata.xml.md5
tmp/localdomain/localhost/mdeploy-138-poc/maven-metadata.xml.sha1


> can't upload existing jar+pom as one snapshot artifact
> ------------------------------------------------------
>
>                 Key: MDEPLOY-138
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-138
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>            Reporter: Olaf Klischat
>
> There seems to be no way to reliably deploy an existing JAR file plus an accompanying, existing POM file (created w/ ivy) that contains the JAR file's metadata and dependencies, to a maven repository.
> If I run
> mvn deploy:deploy-file -Dfile=mylib.jar DpomFile=mypom.pom -DgeneratePom=false -Durl=<repourl>
> , Maven 3 apparently just uploads the jar and names it <groupid-artifactid_from_mypom.pom>-<timestamp>.pom (!)
> (people on maven-users say that this is probably a bug -- http://maven.40175.n5.nabble.com/uploading-existing-jar-pom-as-one-artifact-td4577118.html)
> Maven 2.2 only uploads the POM -- not what was requested either.
> So the problem remains -- how can I reliably deploy and existing jar and pom as one artifact, with the same timestamp/build number.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira