Hi, I've been dealing with much the same requirement. I think you'll want to use the assembly plugin in order to "pack them again," and you'll want the resulting EJB artifact to be a dependency for the project that builds the EAR.
Just an observation: intuitively this approach strikes me as antithetical to some core Maven values and even basic "good practices" like factoring out commonality, etc. I limit its application to a very narrow use case. Specifically, I only use this approach for the situation where I require the ability to deploy, into a single appserver, multiple instances of the same application that are guaranteed to be identical except as regards their configuration as obtained from the various deployment descriptors (e.g., context roots, data source bindings, etc.). To the extent possible (and practicable) I obviate this problem by refactoring. Mark Sergio Rodriguez wrote: > > Hello, > > I have an EJB project that is a dependency of several of my projects. I > need to modify the JNDI name at the EJB's jboss.xml so I can deploy > several apps on the same jboss server. > > How can I filter the resources of an already-compiled dependency? I have > tried to unpack-dependencies and filter them, but don't know how to pack > them again into a new EJB for my EAR. > > Any suggestions? > -- View this message in context: http://www.nabble.com/how-can-I-filter-the-resources-of-one-of-the-dependencies-before-building-an-EAR--tp24160990p24166045.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
