Activity report on *[JIRA] Bug SKER4656 - sesat-mojo:deploy runs twice during non-development builds*
Scarab Link: http://sesat.no/scarab/issues/id/SKER4656 Module: Sesat> Kernel Activity generated by Mick Semb Wever ([EMAIL PROTECTED]) at 05/13/2008 13:49 *Reasons for the changes* *Comments* - By Mick Semb Wever - 05/13/2008 13:53 --- "I see the problem as being that when you enabled the include-fast profile then the sesat-mojo:deploy goal is attached to the install phase. This is only applicable if the development profile is enabled." - By Mick Semb Wever - 05/13/2008 13:49 --- "I can confirm that this does not work yet in 2.17. (You don't need permissions to restart basefarm tomcats to see). cd sesat-kernel-2.17 mvn install -Pinclude-fast,nuclei -Duser.name=junk -DskipTests=true leads to: {code}[INFO] Uploading /home/mick/.m2/repository/sesat/generic.sesam.no/2.17-SNAPSHOT/generic.sesam.no-2.17-SNAPSHOT-nuclei.war to scpexe://sch-login01.osl.basefarm.net/www/schibstedsok/nuclei.test.sesam.no/generic.nuclei.test.sesam.war [ERROR] org.apache.maven.wagon.TransferFailedException: Error executing command for transfer at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:290) at no.sesat.mojo.DeploySesatWarfilesMojo.executeServerDeploy(DeploySesatWarfilesMojo.java:356) at no.sesat.mojo.DeploySesatWarfilesMojo.execute(DeploySesatWarfilesMojo.java:293){code} "
_______________________________________________ Kernel-issues mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-issues
