[
http://jira.codehaus.org/browse/MTOMCAT-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210689#action_210689
]
Dennis Lundberg commented on MTOMCAT-4:
---------------------------------------
I'm not sure I follow you Mark.
1. In my experience finalName is set to something shorter than artifactId. The
reason for it being that the URL will be less cumbersome. An example from a
multi module build might clarify. ArtifactId for the webapp module is
'mycompany-product-webapp' and finalName is set to 'product'. This make the URL
to the webapp during development 'http://development-server:8080/product'. Nice
and clean.
2. The problem I have with the change that was made is that it affects all
goals, not only the run goals. It affects all deploy goals as well. So in an
environment like ours where the production URL never includes the artifactId,
but rather finalName, we have to configure the Tomcat Plugin for every webapp
to be able to deploy them.
> 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
