I have a Maven build that runs fine on the master, but when it runs on the 
slave it fails.  The pom.xml that drives the maven build has a custom execution 
statement that appears to use a property setting in the same file.  The file 
has the following. Is it possible that the slave is not passing ${basedir} 
properly?


    <build>

        <plugins>

            <plugin>

               <groupId>org.apache.maven.plugins</groupId>

               <artifactId>maven-install-plugin</artifactId>

               <version>2.5.2</version>

               <executions>

                   <execution>

                       <id>install-obsidian.jar</id>

                       <goals>

                           <goal>install-file</goal>

                       </goals>

                       <phase>validate</phase>

                       <configuration>

                           <groupId>company</groupId>

                          <artifactId>obsidian</artifactId>

                           <version>1.0</version>

                           <packaging>jar</packaging>

                          <file>${obsidian.path}/obsidian.jar</file>

                           <generatePom>true</generatePom>

                       </configuration>

                   </execution>

                    

     <properties>        
<obsidian.jar.path>${basedir}/src/main/lib</obsidian.jar.path>
        <obsidian.war.path>${basedir}</obsidian.war.path>
        <powermock.version>1.6.2</powermock.version>

    </properties>

 

 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/729725656.1084633.1436796915201.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to