jira-importer commented on issue #240: URL: https://github.com/apache/maven-war-plugin/issues/240#issuecomment-2967855075
**[Marcel May](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=marcelmay)** commented The cause of the different maven-war-plugin versions is a mystery ... I would expect mvn to use the 2.0 version configured for simple-partial-update project, when building from the subproject and from the top since it is defined so in the subproject POM.. Maybe check what "mvn projecthelp\:effective-pom" says for the top and for the subproject... Sorry, can't build the source code since some deps are missing (javax.servlet.jsp:jsp-api), and http://download.java.net/javaee5/external/shared repo is not accessible (from outside of Sun I guess :-)) BTW, I recommend you use a central pluginManagement entry for plugin versions/defaul config management, and a central dependencyManagement section. That way, you avoid spreading dependency and plugin version configuration all over your POMs. Like in you master pom, which already contains the compiler plugin. Maybe this will work for your maven-war-plugin version problem at the moment, too. -- 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
