Hi, This has been tackled a dozen of times and I am not sure it has anything to do with the EAR plugin, at least if we follow the spec. If I am wrong, please let me know.
The valid way to bundle shared components/libs in a EAR is to define the Class-Path entry of the manifest in EJB module(s) using the component. It's certainly not by adding them in a <java> module entry in the application.xml even though some application servers support this (JBoss namely). The EAR plugin supports the APP-INF/lib weblogic's trick by using the defaultJarBundleDir setting though. So I wouldn't say the EAR plugin has no dependency management features at all, I don't even see the point actually :) Make sure that your classpath entries got generated on the EJB side and it will just run fine. Now I agree it's not always easy so if you have ideas to improve, let us know. I am not sure we can do something at the EAR level, except generating EARs that do not follow the spec. Cheers, Stéphane On 12/14/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Hi all, Using the v2.3-SNAPSHOT version of the ear plugin, I am struggling to get the application.xml file built correctly. Between maven1 and maven2, the ejb plugin lost it's ability to bundle dependencies inside the ejb. This means (as I understand it) that it's now up to the ear plugin to add all the dependencies to the application.xml file. However, it seems that the maven-ear-plugin does not have any documented functionality to add dependencies to application.xml, except for explicitly declaring dependencies using the jarModule tag. This duplicates the dependency list, and removes all the power behind transitive dependency management, which is supposed to handle dependencies for you. Is there a setting I am not seeing, or does the ear plugin have no dependency management features at all? Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
