[
http://jira.codehaus.org/browse/MTOMCAT-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210692#action_210692
]
Mark Hobson commented on MTOMCAT-4:
-----------------------------------
In my example I was using the default final name, hence the Tomcat path ==
finalName == artifactId-version.
I understand your scenario though. How about configuring the Tomcat plugin in
a parent POM to set the path to a property, say ${tomcatPath}, and then just
supplying a value to this property in child POMs?
If you feel strongly about it then perhaps start a vote on the mojo-dev list
and see what the consensus is.
> Change default web context to artifact id for run goals
> -------------------------------------------------------
>
> Key: MTOMCAT-4
> URL: http://jira.codehaus.org/browse/MTOMCAT-4
> Project: Maven 2.x Tomcat Plugin
> Issue Type: Improvement
> Reporter: Mark Hobson
> Assignee: Mark Hobson
> Priority: Minor
> Fix For: 1.0-beta-1
>
>
> Currently the default web context is the artifact's final name which by
> default is artifactId-version. It'd be better to default to the artifact id
> instead, as per jetty's plugin.
--
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
