[MINSTALL-3] The install plugin fails if there are only "attached" artifacts.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1
• Assignee: Brett Porter
• Reporter: jps
• Created: 18/Nov/05 05:14
• Updated: 01/Jan/09 06:58
• Resolved: 03/Jan/06 23:16

Description

Usually, classifiers are used to produce attached artifacts, together with the "main" artifact. In some cases, however, it is not possible to produce the different flavors of the artifacts simultaneously (for example, for a version with debug and without debug).

Then, in order to have a single artifact with a classifier, one can configure the jar plugin as follow:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<classifier>someclassifier</classifier>
</configuration>
</plugin>

However, this cause the install plugin (and probably also the deploy plugin) to fail, because it cannot find the "main" artifact:

[INFO] [jar:jar]
[INFO] Building jar: /home/julien/cvs/java/libs/attr/target/libattr-3.0-nodebug.jar
[INFO] [install:install]
[INFO] Installing /home/julien/cvs/java/libs/attr/target/classes to /home/julien/.m2/repository/unicity/libattr/3.0/libattr-3.0.jar

Issue Links

• relates to: MINSTALL-18 Bad algorithm to decide if the main artifact is to be installed or not