[
http://jira.codehaus.org/browse/MTOMCAT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236960#action_236960
]
Mark Michaelis commented on MTOMCAT-63:
---------------------------------------
Actually my real problem was described in MTOMCAT-55. This issue is not really
required but it makes sense to resolve it to make the isWar check consistent.
> Make isWar() check consistent with MTOMCAT-23
> ---------------------------------------------
>
> Key: MTOMCAT-63
> URL: http://jira.codehaus.org/browse/MTOMCAT-63
> Project: Maven 2.x Tomcat Plugin
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Mark Michaelis
> Attachments: MTOMCAT-63.patch
>
>
> Apply the change of MTOMCAT-23 to all other isWar checks - especially to
> {{org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo}} which should be equal to
> {{org.codehaus.mojo.tomcat.AbstractRunMojo}}.
> *Background:* We use the maven-tomcat-plugin for integration tests and the
> WAR comes from another module. So while we can use tomcat:run-war to start
> the Tomcat with the Webapp (we unpacked it before) we have no chance to stop
> the tomcat after the integration tests are done.
--
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
