[
http://jira.codehaus.org/browse/MTOMCAT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163402#action_163402
]
Louis Letourneau commented on MTOMCAT-21:
-----------------------------------------
The workaround is actually this:
<configuration>
<path>/${project.build.finalName}</path>
</configuration>
> MTOMCAT-4 forces users to use the path configuration instead of just setting
> the finalName node in the pom
> ----------------------------------------------------------------------------------------------------------
>
> Key: MTOMCAT-21
> URL: http://jira.codehaus.org/browse/MTOMCAT-21
> Project: Maven 2.x Tomcat Plugin
> Issue Type: Bug
> Affects Versions: 1.0-beta-1
> Reporter: Louis Letourneau
>
> MTOMCAT-4 'breaks' what the documentation says in regards to overriding the
> finalName to set the war name:
> http://mojo.codehaus.org/tomcat-maven-plugin/usage.html
> section
> Using a different context path
> The only way to do this now is to override the path in configuration like
> this:
> <configuration>
> <path>/mycontext</path>
> </configuration>
--
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
