jira-importer commented on issue #170: URL: https://github.com/apache/maven-war-plugin/issues/170#issuecomment-2967847465
**[Mike Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)** commented This is more of a documentation issue than anything. The EAR and WAR plugins already support the features required to move ALL war dependencies to the EAR with some caveats. This is the email I sent to the user list today: We throw everything in <EAR_ROOT>/lib and exclude them from WEB-INF/lib. The WAR's MANIFEST.MF is autogenerated like so: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <configuration> <warSourceExcludes>WEB-INF/lib/*.jar</warSourceExcludes> <archive> <manifest> <addClasspath>true</addClasspath> <classpathPrefix>lib/</classpathPrefix> </manifest> </archive> </configuration> </plugin> In the EAR's POM, you need to list all the dependencies that the WARs have as direct dependencies in the EAR. This will tell the plugin to copy all dependent jars to <EAR_ROOT>/lib. <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-ear-plugin</artifactId> <configuration> <defaultJavaBundleDir>lib/</defaultJavaBundleDir> </configuration> </plugin> -- 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
