maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl-Heinz Marbaise (JIRA)" <j...@codehaus.org>
Subject [jira] (MEAR-168) Use build final name as default context root
Date Tue, 17 Feb 2015 19:43:18 GMT

     [ https://jira.codehaus.org/browse/MEAR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl-Heinz Marbaise closed MEAR-168.
------------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: waiting-for-feedback)
         Assignee: Karl-Heinz Marbaise

Unfortunately no feedback. Please don't hesitate to reopen the issue if you have further informations.

> Use build final name as default context root
> --------------------------------------------
>
>                 Key: MEAR-168
>                 URL: https://jira.codehaus.org/browse/MEAR-168
>             Project: Maven Ear Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.8
>         Environment: all
>            Reporter: José Volmei Dal Prá Junior
>            Assignee: Karl-Heinz Marbaise
>         Attachments: pom.xml, WebModule.java
>
>
> Sometimes we need to make some conventions when dealing with several modules. We need
to use the "$\{project.build.finalName}" as the default "contextRoot" mapping.
> The suggestion is: make a global configuration parameter with name "mustUseBuildFinalNameAsDefaultWebContextRoot".
If this is set to true then the "WebModule.getDefaultContextRoot" method must use the build
final name as context root.
> The global configuration parameter should have false as default value.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message