jira-importer commented on issue #95: URL: https://github.com/apache/maven-war-plugin/issues/95#issuecomment-2967841963
**[Fabrice Bellingard](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fabemn)** commented Well, I'm not sure this bug is fixed... I've just tested the following configuration (2.0-beta-2 has just been released, and which seems to have your patch): <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.0-beta-2</version> <configuration> <warSourceExcludes>**/lib/*.jar</warSourceExcludes> </configuration> </plugin> and all the JARs are still excluded from the packaging. Looking at the code, #getExcludes (which uses the 'warSourceExcludes' property) is indeed called in AbstractWarMojo#copyResources, but it is also called in WarMojo#performPackaging, which results in excluding all the JARs from the WAR - even the JARs that come from the pom dependencies. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
