[
https://jira.codehaus.org/browse/MEAR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MEAR-113.
------------------------------------
Resolution: Cannot Reproduce
Assignee: Karl-Heinz Marbaise
Based on the age of the issue i will close the issue. If you have any
objections or new information etc. don't hesitate to reopen the issue.
> The default contextRoot should match the default bundleFileName
> ---------------------------------------------------------------
>
> Key: MEAR-113
> URL: https://jira.codehaus.org/browse/MEAR-113
> Project: Maven Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.2
> Reporter: Michael Semb Wever
> Assignee: Karl-Heinz Marbaise
> Attachments: MEAR-113.patch, MEAR-113.patch
>
>
> In a webModule the contextRoot defaults to
> "/" + a.getArtifactId()
> There is no way AFAIK to have a contextRoot that honours the webModule
> artifact's finalName, necessary if it was dynamically set via profiles.
> (The only way i see here is to duplicate all the profile information and put
> the maven-ear-plugin configuration into each profile, just to insert the
> various contextRoot values).
> By making the contextRoot instead default to
> "/" + getBundleFileName()
> this scenario is solved.
> The webModule's contextRoot defaults to the build name of the artifact if it
> were customised. If that artifact's finalName was not customised then it
> defaults back to the artifactId therefore maintaining today's behavior and
> not breaking any compatibility.
> Patch attached.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
