[
https://issues.apache.org/jira/browse/MTOMCAT-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov resolved MTOMCAT-79.
-----------------------------------
Resolution: Not A Problem
Fix Version/s: 1.1
I did not notice the "deploy-only" mojo. It does exactly the same but does not
fork the package phase.
> Running "package" before tomcat:deploy breaks build
> ---------------------------------------------------
>
> Key: MTOMCAT-79
> URL: https://issues.apache.org/jira/browse/MTOMCAT-79
> Project: Maven 2.x Tomcat Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: Maven 2.2.11
> Reporter: Michael Osipov
> Priority: Blocker
> Fix For: 1.1
>
>
> @execute="package" breaks multi-module builds with overlays.
> I have this situation:
> {noformat}
> parent
> |-war1
> |-war2 (overlayed with war1)
> {noformat}
> To have war2 overlayed with war1 from reactor, I have to build from parent.
> I.e., to deploy a correctly overlayed war2, I have to have to go from parent.
> Otherwise overlay happens from local repo which is incorrect. So, because
> tomcat-maven-p invokes "package" at war2 and only at war2, the overlay war1
> is taken from local repo. The overlayed WAR is incorrect. I explicitly have
> to call "package" from parent.
> I have logs available which prove the issue but cannot make them public. I
> can send them privately.
> All this means, that the automatic execution of package needs to be removed.
> If there is no warFile to deploy, exit with build failure and tell that
> package has to run first.
> Remove this line:
> http://mojo.codehaus.org/tomcat-maven-plugin/xref/org/codehaus/mojo/tomcat/DeployMojo.html#26
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
