> -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: jeudi 28 avril 2005 09:36 > To: Cactus Developers List > Cc: [EMAIL PROTECTED] > Subject: Re: [EMAIL PROTECTED]: Project jakarta-cactus-integration-ant-12 (in > module jakarta-cactus) failed > > On Thu, 28 Apr 2005, Vincent Massol <[EMAIL PROTECTED]> wrote: > > From: Stefan Bodewig > > >> I've split it into cargo-core and cargo-ant since they seemed to > >> create independent artifacts. No idea if/how it is going to turn > >> out. > > > > Does the Maven integration in Gump let Maven handle multiprojects > > No idea, never tried that. Would we need to do anything special to > allow it?
The question is really whether we want to hardcode the dependencies between Cargo subprojects or let Maven handle this. The fact that you mention defining cargo-core and cargo-ant subprojects in the Gump descriptor led me to believe that maybe Gump does not support building a top level project. So my question is really: why don't we try having Gump build the whole Maven project by having a single cargo module in Gump? > > This doc (http://cargo.codehaus.org/Project+Structure) shows the > > Cargo build structure. > > Judging from this - assuming multiprojects woudn't work - we'd need to > have three "project"s in cargo-core, one in ant and one in maven. > Which one would the Ant integration in cactsu need? Actually we would need the following to get the Ant integration: - cargo-core/ - cargo-ant/ - samples/testdata/*/ - samples/java/ - samples/ant - distribution/ [snip] Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
