maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stéphane Nicoll (JIRA) <j...@codehaus.org>
Subject [jira] (MEAR-168) Use build final name as default context root
Date Sat, 09 Feb 2013 15:33:13 GMT

    [ https://jira.codehaus.org/browse/MEAR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318881#comment-318881
] 

Stéphane Nicoll edited comment on MEAR-168 at 2/9/13 9:32 AM:
--------------------------------------------------------------

2.8.1 and 2.9 are not even released so you can't be affected by those.
                
      was (Author: sni):
    2.8.1 and 2.9 are not even released so you can be affected by those.
                  
> Use build final name as default context root
> --------------------------------------------
>
>                 Key: MEAR-168
>                 URL: https://jira.codehaus.org/browse/MEAR-168
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.8
>         Environment: all
>            Reporter: José Volmei Dal Prá Junior
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message