To promote to release you will have to promote it to the release artifactory not the snapshot artifcatory. If your project.version contains SNAPSHOT (example: 1.2-SNAPSHOT) and you execute mvn deploy, artifacts will be deployed to your snapshot repository. If it doesn't (example: 1.2) - they will be deployed to your release repository. The whole point of a release build is to remove the SNAPSHOT at the version. You can't manually remove SNAPSHOT you have to use the mvn:release plugin. The release plugin will perform the following tasks
* Check that there are no uncommitted changes in the sources * Check that there are no SNAPSHOT dependencies * Change the version in the POMs from x-SNAPSHOT to a new version (you will be prompted for the versions to use) * Transform the SCM information in the POM to include the final destination of the tag * Run the project tests against the modified POMs to confirm everything is in working order * Commit the modified POMs Make sure to have a solid release build project, because you dont want to be deploying SNAPSHOT artifacts to production. No way! This URL should have all the info you need http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html -- View this message in context: http://forums.jfrog.org/Promoting-1-0-0-SNAPSHOT-to-Release-tp7580293p7580299.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
