It would much more powerful to perform that transformation when you actually deploy the artifacts on the server instead of burning the value in something you could potentially deploy on the repository
I would leave the token in the file and add a filtering procedure when the app is built and deployed. You lost the ability to copy an ear right the way but you could have that with a separate project that relies on your ear and perform the transformation for you. S. On Tue, Jun 23, 2009 at 9:10 AM, Sergio Rodriguez <srodrig...@teralco.com>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--tp24160990p24160990.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 > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge
