jira-importer commented on issue #124: URL: https://github.com/apache/maven-war-plugin/issues/124#issuecomment-2967844053
**[Marc Rohlfs](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=marc.rohlfs)** commented I know that in overlays you must take special care about dependencies vs. libs from base WARs. But that is not the issue here. The dependencies I don't want to have are given transitively through the _jar-module_ dependency. The _jar-module_ dependency has _provided_ scope and its transitive dependencies must not be added to the resulting WAR artifact (see scope matrix at [Introduction to the Dependency Mechanism - Dependency Scope](https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope)). But in the given project setup they are add. For further demonstration, I added another dependency _mysql-connector-java_ to the _jar-module_, which is not in the base WAR. It also should not be added to the WAR artifact. This time, I didn't upload another version of the ZIP file. I provided it the sample project on GitHub now (see a lot easier to me): https://github.com/marcrohlfs/MWAR-294. Please test it with +Maven 2.2.1+ and +Maven 3.x+. You'll notice that with Maven +2.2.1+ it works like expected/documented and the unwanted dependencies are not added - but when running the build with +Maven 3.x+, they are added. -- 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
