[
https://issues.apache.org/jira/browse/MDEPLOY-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965707#comment-17965707
]
Olivier Lamy commented on MDEPLOY-138:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#275|https://github.com/apache/maven-deploy-plugin/issues/275].
> can't upload existing jar+pom as one snapshot artifact
> ------------------------------------------------------
>
> Key: MDEPLOY-138
> URL: https://issues.apache.org/jira/browse/MDEPLOY-138
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Olaf Klischat
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
