jira-importer commented on issue #190: URL: https://github.com/apache/maven-war-plugin/issues/190#issuecomment-2967849153
**[Al Robertson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=al.robertson)** commented I am surprised this is marked as fixed. I don't believe it is. Here is a structure that J2EE requires you to support ear jar1 war ->manifest classpath:jar1 jar2 war depends on jar1 and jar2 Currently, you can specify to add a manifest classpath entry. This adds an entry for each dependency that is not "Provided", because provided means "provided by the container". (CORRECT) In the above example, I can't configure maven to exclude jar1 from the war/WEB-INF/lib dir but include it in the classpath manifest. It appears to me that we need another dependency attribute to accompany scope "Provided", say \<providedByManifestClasspath>true\</providedByManifestClasspath> or a \<providedBy>CONTAINER|MF-CP\</providedBy> etc. In this solution, we wouldn't need the manifest->addClasspath plugin config. The war builder would only include the artifact in the war when the scope wasn't provided and the war archiver would know when to include the dependency in the manifest classpath. You would still require the manifest classpath prefix config. Does this make sense? Is there a way to accomplish this already? -- 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
