Jason van Zyl wrote:

Ok, I have a new portable bundle.

To get rid of the requirement on cygwin: You could use the Os class from plexus-utils to detect Windows and set a flag in the Velocity context for the templates. Using this flag, the templates could be tweaked to use batch files instead of shell scripts for the Maven launches.

For maven-2.1.x-IT-support.xml:

    <hudson.tasks.BatchFile>
      <command>
set "M2_HOME=${hudsonHome}\apache-maven-2.1-SNAPSHOT"
"${hudsonHome}\apache-maven-2.1-SNAPSHOT\bin\mvn" -f "%WORKSPACE%\core-integration-tests-support\pom.xml" "-Dmaven.repo.local=${mavenRepoLocal}" clean install
      </command>
    </hudson.tasks.BatchFile>

And for maven-2.1.x-ITs.xml:

    <hudson.tasks.BatchFile>
      <command>
set "M2_HOME=${hudsonHome}\apache-maven-2.1-SNAPSHOT"
"${hudsonHome}\apache-maven-2.1-SNAPSHOT\bin\mvn" -f "%WORKSPACE%\core-integration-tests\pom.xml" "-Dmaven.repo.local=${mavenRepoLocal}" -Prun-its clean test
      </command>
    </hudson.tasks.BatchFile>

BTW, the template for maven-2.1.x-ITs.xml still contains the old placeholders @HUDSON_HOME@ and @REPO@, making it produce a non-functional config.xml.


Benjamin

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to