Hello I have an ear which in turn has dependencies that need to be furnished to all sub projects (a few EJBs, a few WARs). The maven build itself is configured to do the right thing and, in the resulting .ear, yeilds an APP-INF/lib director with all non ejb/war/car dependencies.
I can even run mvn eclipse:eclipse with the wtp support and get a pretty useful setup inside of eclipse. I also setup maven to not generate -SNAPSHOT-1.0.jar on the artifacts, which makes the application.xml something we can keep in source. This in turn makes eclipse happy because it can let us use the WTP facilities for an EAR. However, when we take the ear project and add it to a server (JBoss), and then publish that eclipse project, eclipse builds an ear (amazingly !) that works just like if mvn had built it EXCEPT for /APP-INF/lib/*jar at the root of the ear project. Apparently this has something to do with the EAR Libraries library, but I'm unsure of how to accomodate this. Plus, it ideally should be correctly configured by the mavne plugin. Does anyone have any way around this? A custom mojo I might bind to the eclipse:eclipse phase? Insight on how this would be configured in the low level eclipse .settings stufff? Anything at all would be appreciated. Thanks, Josh Long --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
