Not an issue. The definition of the jar plugin in the parent pom conflicts with war

FYI: We've found that if you add a classifier to the jar that causes the filename to differ from the .war file, the install:install step will grab both and not exhibt the issue described here.

i.e.

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<id>my-web-jar</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<classifier>something</classifier>
</configuration>
</execution>
</executions>
</plugin>

(Although a better solution is to refactor your jar content into a "common" module though)

It would be great if this would be fixed. It seems the maven-source-plugin works properly, but the maven-war-plugin does not. I would like to generate primary and secondary artifacts using a single pom file. It seems overly complex to have to make modules out of everything.

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<id>default-jar</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>

<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<warName>cds_commons</warName>
</configuration>
<executions>
<execution>
<id>attach-war</id>
<phase>package</phase>
<goals>
<goal>war</goal>
</goals>
</execution>
</executions>
</plugin>

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-sources</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
< /plugins>
</build>

Rich, this issue is already closed as "Won't Fix" indicating that the developers don't consider it a valid bug. You might want to bring it up on the mailing list if you feel it should be re-opened. Otherwise, nothing is likely to happen with it.