[
https://issues.jenkins-ci.org/browse/JENKINS-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Thome updated JENKINS-12950:
----------------------------------
I stumbled across someone else who ran into this issue. The work-around was to
run 'mvn install'. Somehow, this created the right chain of events for the
upload to work correctly.
It seems to me, that as long as the JAR and POM are in the standard maven
locations, the deploy should work correctly (from a user experience
perspective). I did not see any documentation which directed Maven users to
first run an install. I guess, if this plug-in is strategically replacing the
'deploy', then executing the 'install' might make sense... but it wasn't
intuitive.
Just looking for comment. Thanks.
> pom.xml not deploying to Artifactory
> ------------------------------------
>
> Key: JENKINS-12950
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12950
> Project: Jenkins
> Issue Type: Bug
> Components: artifactory
> Reporter: Jerry Thome
> Assignee: yossis
> Attachments: 3-1-2012 10-38-30 AM.png
>
>
> Jenkins ver. 1.444
> Jenkins Artifactory Plugin 2.0.5
> Maven 3.0.3
> We have a very simple Maven project setup. We are running "clean package
> verify emma:emma" and then using the Artifactory plugin to publish to a
> snapshot repository in Artifactory.
> We simlpy want the basic pom.xml and jar deployed, but only the JAR is being
> deployed. If I use the standard 'mvn deploy' or the "Deploy artifacts to
> Maven repository", it works as expected.
> Do we need to configure something special in the "Include Patterns"?
> Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
