I've searched on this and from what I can tell, this question has not been directly asked before...
I have an EAR artifact that declares dependencies on several of my own jars, a war, and some 3rd party jars. This is sufficient to get the artifacts included in my EAR, however, if I actually want an artifact to be included in application.xml (so it is actually accessible at runtime), I need to pretty much duplicate the dependency list in the modules section of the ear-plugin config. I am wondering if I am doing something incorrectly, as this duplication seems somewhat contrary to maven's principle of 'useful defaults' (which IMO would include declared dependencies in the application.xml unless you explicitly exclude them). Or am I misunderstanding the relationship between application.xml and the runtime classpath. (i.e. should I be instead using a generated ear manifest for the classpath). Thanks, Shea. -- View this message in context: http://www.nabble.com/m2-ear-plugin-and-streamlining-config-of-application.xml-generation-tf3176492s177.html#a8813645 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
