[
http://jira.codehaus.org/browse/MTOMCAT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MTOMCAT-1.
------------------------------
Resolution: Fixed
fixed in rev [8743|http://fisheye.codehaus.org/changelog/mojo/?cs=8743]
> Having a deploy mojo which doesn't fork a lifecycle
> ---------------------------------------------------
>
> Key: MTOMCAT-1
> URL: http://jira.codehaus.org/browse/MTOMCAT-1
> Project: Maven 2.x Tomcat Plugin
> Issue Type: Improvement
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Fix For: 1.0-alpha-2
>
>
> In my ci server or with the cli, I activate deploying a war in a integration
> tomcat server.
> This is currently activated in a profile. If I use the deploy mojo a new
> package lifecycle is forked which is really time consuming.
> The mojo could be nammed OnlyDeploy, goal : only-deploy
--
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 from this list, please visit:
http://xircles.codehaus.org/manage_email
