[jira] [Updated] (MTOMCAT-155) allow exec-war war run dependencies that are generated in current mvn execuion, but not yet installed to maven repo

["Peter lynch (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MTOMCAT-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter lynch updated MTOMCAT-155:
--------------------------------

    Attachment: warRunDependency-in-current-execution.patch

attached patch
                
> allow exec-war war run dependencies that are generated in current mvn execuion, 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org