Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-3205

Maven builds fail when using packaging extensions and classifier

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: Linux

      I have a build that is running fine via command-line on the hudson box (as the
      hudson user on the hudson workspace), but is failing inside hudson.

      Here's the relevant sections of the pom:

      <project xmlns="http://maven.apache.org/POM/4.0.0"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
      http://maven.apache.org/maven-v4_0_0.xsd">
      <parent>
      <artifactId>web-parent</artifactId>
      <groupId>com.fortisphere.web</groupId>
      <version>1.0-SNAPSHOT</version>
      </parent>
      <modelVersion>4.0.0</modelVersion>
      <groupId>com.fortisphere.web</groupId>
      <artifactId>webapp</artifactId>
      <packaging>war</packaging>
      <version>1.0-SNAPSHOT</version>
      <build>
      <plugins>
      <plugin>
      <groupId>org.codehaus.mojo.javascript</groupId>
      <artifactId>javascript-maven-plugin</artifactId>
      <version>1.0-alpha-1-SNAPSHOT</version>
      <extensions>true</extensions>
      <configuration>
      <scriptsDirectory>javascript</scriptsDirectory>
      <libsDirectory>lib</libsDirectory>
      </configuration>
      <executions>
      <execution>
      <goals>
      <goal>war-package</goal>
      </goals>
      </execution>
      </executions>
      </plugin>
      </plugins>
      </build>
      <dependencies>
      <dependency>
      <groupId>com.fortisphere.web</groupId>
      <artifactId>js-libs</artifactId>
      <version>1.0-SNAPSHOT</version>
      <type>javascript</type>
      </dependency>
      </dependencies>
      <profiles>
      <!-- TODO - Alternative methods of creating "final" ports? -->
      <profile>
      <id>hudson</id>
      <activation>
      <property>
      <name>env.BUILD_NUMBER</name>
      </property>
      </activation>
      <properties>
      <build.version>${env.BUILD_NUMBER}</build.version>
      <httpPort>80</httpPort>
      <httpsPort>443</httpsPort>
      </properties>
      <!-- Expands the minified javascript into our webapp when building on
      hudson. -->
      <dependencies>
      <dependency>
      <groupId>com.fortisphere.web</groupId>
      <artifactId>js-libs</artifactId>
      <version>1.0-SNAPSHOT</version>
      <type>javascript</type>
      <classifier>compressed</classifier>
      </dependency>
      </dependencies>
      </profile>
      </profiles>
      </project>

      The issue appears to be hudson is trying to find
      "js-libs-1.0-SNAPSHOT-compressed.javascript" instead of
      "js-libs-1.0-SNAPSHOT-compressed.jar". The maven-javascript-plugin
      <extensions>true</extensions> is supposed to be handling this.

          [JENKINS-3205] Maven builds fail when using packaging extensions and classifier

          There are no comments yet on this issue.

            Unassigned Unassigned
            jsuereth jsuereth
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: