There was a similar thread (however for glassfish) today. Have a look at my answer there about having a separate project for the deployment to glassfish/tomcat.
/Anders On Tue, Sep 15, 2009 at 21:18, James Russo <[email protected]> wrote: > Hello, > > I'm likely just not going this the right way.. Have a project with 5 > modules or so, one of which is a war. I'd like to be able to use > cargo:deploy on the parent project and have it work to deploy the war. The > problem is that it stops at my first module saying "artifact xyz isn't a > dependency of common".. Which is true. > > The reason for this is I'd like to have hudson automatically deploy (via > maven) the latest war to tomcat. Seems like tomcat:deploy automatically > skips modules where the artifact is not "war", not sure how I could achieve > the same thing using cargo. > > -jr > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
