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

Roman Kitko commented on MWAR-188:
----------------------------------

Ok, Dennis thanks for quick reply.

For the future, if you change backward compatibility, users must be better 
informed about the change.
I hope I just miss some information channel.

> 2.1-beta-1 ignores warSourceExcludes
> ------------------------------------
>
>                 Key: MWAR-188
>                 URL: http://jira.codehaus.org/browse/MWAR-188
>             Project: Maven 2.x WAR Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-beta-1
>         Environment: Ubuntu 8.10, JDK 1.6.10, mvn 2.0.10
>            Reporter: Roman Kitko
>         Attachments: war-excludes-test.zip
>
>
> WAR  plugin again ignores (or for any reason copy dependencies) 
> warSourceExcludes configuation property.
> warSourceExcludes correctly works in 2.1-alpha-1, breaks in 2.1-alpha-2 and 
> 2.1-beta-1. This is regression bug, already reported and fixed for previous 
> version .
> I am sending test zipped project. 
> This is its pom :
>   <dependencies>
>     <dependency>
>       <groupId>commons-logging</groupId>
>       <artifactId>commons-logging</artifactId>
>       <version>1.1.1</version>
>     </dependency>
>   </dependencies>
>   
>   <build>
>       <plugins>
>       <plugin>
>         <artifactId>maven-war-plugin</artifactId>
>         <!-- 2.1-alpha-1 works, 2.1-alpha-2 does not work, 2.1-beta-1 does 
> not work -->
>         <version>2.1-beta-1</version>
>         <configuration>
>           <warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes>
>         </configuration>
>       </plugin>
>       </plugins>
>   </build>

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