jira-importer commented on issue #189: URL: https://github.com/apache/maven-war-plugin/issues/189#issuecomment-2967849022
**[Mark Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)** commented I also discovered this problem today in a production environment. Thanks to the various exclude mechanisms this is easy to fix. But since this a fairly common scenario, we should really try to implement an automated handling. First of all, this problem exists only if one WAR is depending on another WAR, am i right? Is there any other scenario not involving two dependent WAR files? Assuming this, i think the problem is that - since dependencies of WAR files currently are not transitive - we are stuck with the jars comming from the wars WEB-INF/lib. On the other hand, if the dependent WAR file has any dependencies defined in the POM and those would be treated as usual transitive dependencies (keep in mind that this is only valid when a WAR is currently beeing built), we may simply forget about the libs from the dependent WAR and the conflict could be solved by the standard maven mechanism. This also has no negative effect for manually imported WARs (not beeing built with maven). Those WARs simply have no dependencies specified in the POM, so all the libs would be used for overlaying without any exclusion. -- 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
