When a WAR is defined as a dependency of another project, is there any configuration to allow the war's dependencies to be discovered transitively?
This behavior is desired in the scenario where utility JARs are packaged in an EAR, not in the dependent WARs (http://jira.codehaus.org/browse/MWAR-9). In this scenario, it is currently necessary to define all the WAR's dependencies within the WAR's POM, to exclude the contents of the WAR's WEB-INF/lib, and then to duplicate all WARs' dependencies within the EAR's POM. It seems that the WAR type was not intended to support the J2EE packaging strategy which allows utility JARs to be defined in the EAR, and therefore prevents the WAR's dependencies from being discovered transitively. -- View this message in context: http://www.nabble.com/WAR-transitive-dependencies-tf2860612s177.html#a7992662 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
