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
