Hi Jesse, Glad I'm not the only one who is trying such thing. Great solution you just gave me, I hope this works for me as well.
Big thanks! 2009/5/11 <[email protected]> > Hi Bocalinda, > > On Mon, May 11, 2009 at 10:28 AM, Bocalinda <[email protected]> wrote: > > > > In order to achieve automatic testing of my projects, I use Cargo to > > automatically deploy newly generated war files to a Tomcat server. > > All the specifics to the automatic testing (depedencies, plugin > > configuration, etc) are contained inside of a super pom. > > Yep, I find myself in the same position. I don't think the Cargo > plugin is behaving badly here. Instead, you can create a profile in > your super pom which will be automatically activated by a property. > Then, in your Maven modules which are packaging=war, you can set that > property. Ideally, Maven would support profile activation by packaging > type (I believe I created a JIRA for this, or commented in an existing > Profile Enhancement type JIRA) but unfortunately it can not, yet.. > > Anyhow, the solution I propose requires the least amount of specific > per-Maven module configuration and allows the greatest amount > configuration reusability. I have had it working in my environment for > about 6 months of active development for several projects.. > > Good luck! > -jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
