jira-importer commented on issue #247: URL: https://github.com/apache/maven-war-plugin/issues/247#issuecomment-2967855611
**[Mark Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)** commented Hi Carlos! The problem is, that the classes of the war, on which the actual war depends on, are not available at compiletime for the actual war. For example: The class Test2 is in war2 and depends on war1 which has the Test1 class + class Test2 extends Test1 So even if i switch the archiveClasses feature on, the compiler may not see the dependant classes at compile time. What i have done so far to resolve this issue (i would rather consider it a bug) is to introduce a new WarClasspathMojo which temporary explodes any dependant war and adds a resourcePath to the target/$explodedWarPath/WEB-INF/classes directory. Since the maven-war-plugin is only active if the actual artifact is a war, this has imho no negative effects on building e.g. an EAR where this is not intended. The new WarClasspathMojo is to be activated in the phase generate-resources. -- 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
