[
https://issues.apache.org/jira/browse/MTOMCAT-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280182#comment-13280182
]
Peter lynch edited comment on MTOMCAT-155 at 5/21/12 2:35 PM:
--------------------------------------------------------------
Suppose the Maven project both creates the non exec war (A), to be included as
a warRunDependency in exec-war-only goal and also the exec-war war (B) which
will use (A) in the same Maven execution. Since (A) and (B) creation happens
in package phase, before install phase, artifact.getFile() of warRunDependency
resolves to {{./target/A.war}} instead of somewhere in {{ ~/.m2/repository}}.
Old code tried to copy from {{./target/A.war to {{./target/A.war}} in this case
before modifying the warRunDependency and failed because file already existed.
was (Author: peterlynch):
Suppose the Maven project both creates the non exec war (A), to be included
as a warRunDependency in exec-war-only goal and also the exec-war war (B) which
will use (A) in the same Maven execution. Since (A) and (B) creation happens
in package phase, before install phase, artifact.getFile() of warRunDependency
resolves to ./target/A.war instead of somewhere in{{ ~/.m2/repository}}. Old
code tried to copy from ./target/mywar.war to ./target/mywar.war in this case
before modifying the warRunDependency and failed because file already existed.
> allow exec-war war run dependencies that are generated in current mvn
> execution, but not yet installed to maven repo
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MTOMCAT-155
> URL: https://issues.apache.org/jira/browse/MTOMCAT-155
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Peter lynch
> Attachments: warRunDependency-in-current-execution.patch
>
>
> If a war run dependency ( used in exec-war) was generated as part of current
> mvn execution maven module as executing tomcat plugin, then artifact file
> will be in target dir and not yet installed into maven repo yet ( since
> install phase has not been run) - so copy from ./target to
> ./target/(pluginWorkDirectory) to allow modifying war run dependency to avoid
> potential attempt of current code to overrite existing target dir exec-war.
> See attached patch file fo fix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
