[ 
http://jira.codehaus.org/browse/MWAR-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231954#action_231954
 ] 

Michiel Meeuwissen commented on MWAR-205:
-----------------------------------------

If files appear in the same directory in different overlays, then that may be 
the case. But normally, files from different overlays appear in different 
directories, and there is no problem in those directories then. 

> A useDefaultExcludes=false option, like the assembly plugin has.
> ----------------------------------------------------------------
>
>                 Key: MWAR-205
>                 URL: http://jira.codehaus.org/browse/MWAR-205
>             Project: Maven 2.x WAR Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.1-beta-1
>         Environment: Linux, tomcat6.
>            Reporter: Michiel Meeuwissen
>         Attachments: useDefaultExcludes.patch
>
>
> I'd like to be able to have a 'development' profile which I configure to 
> _include_ all versioning files. I'm dealing with complicated overlays, and 
> sometimes it's simply easiest to fix a jsp or so directly on the spot where 
> it is deployed, on the test-server or so,  and check it in from there too. 
> Probably I could also change our habits or so, and find some way of working 
> which is more or less handy too, but for the moment I have no idea how that 
> would go, and everything would work just fine if the 'useDefaultExcludes' 
> feature can be disabled with a configuration option.
> I tried to implement it myself, and am attaching a patch, which includes such 
> an option. 
> {code:xml}   
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-war-plugin</artifactId>
>         <version>2.1-beta-2-SNAPSHOT</version>
>         <configuration>
>           <useDefaultExcludes>false</useDefaultExcludes>
>         </configuration>
>       </plugin>
> {code}

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

        

Reply via email to