[MINSTALL-40] install with classifier with no target/classes fails

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.1, 2.2
• Environment: Maven version: 2.0.5, Winx XP pro
• Assignee: Benjamin Bentmann
• Reporter: mork
• Created: 02/Aug/07 05:55
• Updated: 13/Jan/16 00:29
• Resolved: 01/Jan/09 10:10

Description

The install plugin fails with the following error:
Error installing artifact: File C:\TEMP\sample-war\target\classes does not exist
in a project where there is no class or classpath resource generation (so the target/classes folder is not generated in the compile phase).
Suppose for example a war application with no java source code (maybe only jar dependencies) and no classpath resource.
Installing the project as a primary artifact works fine.
Installing the project as a secondary artifact (so with "classifier" option) with classes or resources works fine.
Installing the project as a secondary artifact without classes or resources gives the error below.
Attached is a simple project with packaging WAR composed only by a web.xml file.
Running "mvn install" on this project should give the error above. Commenting the classifier tag will result in a successful install.
Also if I put a simple java file (or a resource) the compile goal will create target/classes folder and the install works fine.
In fact I am using this kind of workaround for the moment (include a dummy resource in the war build).
The same is with a similar jar project (although it may be less useful to have an "empty" jar artifact).
Verified with both maven-install-plugin 2.1 and 2.2

Issue Links

• duplicates: MINSTALL-18 Bad algorithm to decide if the main artifact is to be installed or not
• is related to: MINSTALL-118 MavenProject with only attachments must have packaging "pom"