[
http://jira.codehaus.org/browse/MINSTALL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MINSTALL-40:
--------------------------------------
Attachment: MINSTALL-40-fixed.zip
MINSTALL-40-fixed.zip is an updated version of the example provided by Michele.
This version locks down the version for the maven-install-plugin to 2.3 and
shows this issue is fixed in version 2.3.
So Jesse, be sure to use version 2.3 of the maven-install-plugin. If the issue
really persists for, you will need to provide an example project to reproduce
it for further analysis.
> install with classifier with no target/classes fails
> ----------------------------------------------------
>
> Key: MINSTALL-40
> URL: http://jira.codehaus.org/browse/MINSTALL-40
> 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
> Assignee: Benjamin Bentmann
> Priority: Minor
> Attachments: clean-install-with-war-2.0.2.log, clean-install.log,
> MINSTALL-40-fixed.zip, MINSTALL40-sample2.zip, sample-war.zip
>
>
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
