Okay, what about having CruiseControl call call a script with the following:
$mvn clean deploy $mvn -f pom_legacy.xml deploy Where pom_legacy.xml has the alternate repos defined. Then you could compile once, deploy twice... Kris -----Original Message----- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 12:36 PM To: Maven Users List Subject: RE: [m2] Deploying to more than one repository I'm using CruiseControl now. I'd rather not build the project twice if I can help it... -----Original Message----- From: Bravo, Kris [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 10:09 AM To: Maven Users List Subject: RE: [m2] Deploying to more than one repository You could branch in your scm and maintain two pom.xmls, but you would have to merge to the branch constantly to make sure your legacy branch copy kept up to date. Do you use continuum or another continuous build server? Kris -----Original Message----- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 11:48 AM To: Maven Users List Subject: [m2] Deploying to more than one repository While we transition our projects to Maven 2, I'd like to be able to deploy artifacts built by Maven 2 to our internal Maven 2 repository as well as our internal Maven 1 repository for those project that haven't migrated yet. However, the <distributionManagement> element in the pom will only allow one <repository>. Is there a way to deploy to more than one? I can't use snapshotRepository for it. ..David.. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
