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 Fri, 12 Dec 2014 21:03:10 GMT

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

Karl-Heinz Marbaise commented on MEAR-168:
------------------------------------------

Can you create a real patch and an appropriate integration test to verify the change. Thanks.

> 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
>             Fix For: waiting-for-feedback
>
>         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