[
http://jira.codehaus.org/browse/MINSTALL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125974
]
Dennis Lundberg commented on MINSTALL-40:
-----------------------------------------
I ran the same command that you did and compared the logs. It turns out that
the war plugin that is different. Here's mine:
[DEBUG] maven-war-plugin: resolved to version 2.0-beta-2 from repository central
My log also shows that your version of the war plugin tries to delete more
stuff during clean, than mine does. So perhaps this issue should be moved to
MWAR? When I specify version 2.0 of the war plugin I get the same error as you
do.
Can you confirm that it works for you if you use maven-war-plugin 2.0-beta-2?
> 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
> Priority: Minor
> Attachments: clean-install.log, 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
