You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Piotr Tabor (JIRA)" <ji...@codehaus.org> on 2007/04/06 20:47:02 UTC

[jira] Commented: (MWAR-22) patch to allow extra webapp and webapp/WEB-INF/classes files to be specified that override existing files

    [ http://jira.codehaus.org/browse/MWAR-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92278 ] 

Piotr Tabor commented on MWAR-22:
---------------------------------

I will have to apply an overlay with new resources when 2.1 version will be released . Look at http://jira.codehaus.org/browse/MWAR-97. 

> patch to allow extra webapp and webapp/WEB-INF/classes files to be specified that override existing files
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MWAR-22
>                 URL: http://jira.codehaus.org/browse/MWAR-22
>             Project: Maven 2.x War Plugin
>          Issue Type: Improvement
>            Reporter: Cameron Braid
>         Attachments: maven-war-plugin-extraWarResources.patch
>
>
> Currnelty, there is no way to execute a plugin inbetween the 'build exploded webapp' part of this plugin, and the 'zip up resources' bit.
> I have the need to override classpath resources, and sometimes other webapp resources, based on a deployment target, such as test / staging or production.
> With this patch, I will be able to have files layed out like this :
> /profile/test/config.properties
> /src/main/resources/config.properties
> then configure the war plugin :
>         <configuration>
>         	<extraWebappClasses>profile/test</extraWebappClasses>
>         </configuration>
> thus producing a war that contains profile/test/config.properties instead of the default /src/main/resources/config.properties
> I have investigated alternative ways to achive this goal, and none of them seemed easy.
> Some ideas :
> * split the package phase into 2 phases - preparePackage and package
> * provide a generic technique to allow plugins to expose extension points where other plugins can hook into 
> * create a plugin that runs after the war plugin, that creates a new war - slow since the ziping will need to be done twice
> i'm keen to hear anyone's thoughts on the mailing list or in irc - my nick is Fracture

-- 
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