> However all these artifacts are only really needed when releasing, ie when > calling the deploy phase.
If you change this to: > However all these artifacts are only really needed when releasing, ie when > calling the release plugin. The release plugin uses a release profile, thus you can bind specific plugins only to a release. Calling mvn deploy is not the same as a release, as this will only deploy the current SNAPSHOT version. A release takes multiple steps: tagging, changing versions numbers, checking dependencies, and as last step a deploy to the release repository. (Which is a different one than your snapshot repository.) Take a look at the release plugin: http://maven.apache.org/plugins/maven-release-plugin/ Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, Nov 25, 2008 at 3:36 PM, Yann Albou (JIRA) <[EMAIL PROTECTED]> wrote: > Adding a phase called 'pre-deploy' > ----------------------------------- > > Key: MNG-3869 > URL: http://jira.codehaus.org/browse/MNG-3869 > Project: Maven 2 > Issue Type: New Feature > Components: Plugins and Lifecycle > Affects Versions: 2.1.0-M1, 2.0.9, 2.0.8, 2.0.10, 3.0-alpha-1 > Reporter: Yann Albou > > > Our company policy mandates, for each release, the deployment of the > following artifacts, alongside the usual ones (jar, war, ear): > * for each module: > - sources.jar > - javadocs.jar > * for each EAR: > - a zip assembly > > We use the plugins maven-source-plugin, maven-javadoc-plugin and > maven-assembly-plugin, all binded to the package phase. > > However all these artifacts are only really needed when releasing, ie when > calling the deploy phase. Generating them in the package phase slows down > unnecessarily the developer's builds. > > We tried to bind the plugins to the deploy phase but the default > deploy:deploy goal is always executed before any other goals and the > artifacts aren't deployed. > > The obvious solution would be to have a "pre-deploy" phase where we could > generate these release artifacts, and have them deployed normally in the > deploy phase. > > > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://jira.codehaus.org/secure/Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
