maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michele Lorenzini (JIRA)" <>
Subject [jira] Updated: (MINSTALL-40) install with classifier with no target/classes fails
Date Mon, 03 Mar 2008 09:38:28 GMT


Michele Lorenzini updated MINSTALL-40:

    Attachment: clean-install.log

I've unzipped the sample project, tried a clean install using maven 2.0.7 and version 2.2
of maven-install plugin,
and it does NOT install.
Attached in clean-install.log the complete log (-X) showing what goes wrong for me.
Maybe can be related to some other plugin for which I have some different version?

> install with classifier with no target/classes fails
> ----------------------------------------------------
>                 Key: MINSTALL-40
>                 URL:
>             Project: Maven 2.x Install Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1, 2.2
>         Environment: Maven version: 2.0.5, Winx XP pro
>            Reporter: Michele Lorenzini
>            Priority: Minor
>         Attachments: clean-install.log,
> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message