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

["Wendy Smoak (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MDEPLOY-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak moved MNG-5132 to MDEPLOY-138:
------------------------------------------

           Complexity:   (was: Intermediate)
    Affects Version/s:     (was: 2.2.1)
                           (was: 3.0)
                       2.2.1
                  Key: MDEPLOY-138  (was: MNG-5132)
              Project: Maven 2.x Deploy Plugin  (was: Maven 2 & 3)

> 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