[
https://jira.codehaus.org/browse/MWAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285350#comment-285350
]
Chris Gamache commented on MWAR-269:
------------------------------------
Sure, here's a recipe...
Steps to reproduce:
1. Install Eclipse (tested on Helios and Indigo)
2. Install m2e from update site
http://download.eclipse.org/technology/m2e/releases/
3. Create Maven project for the war deployment
4. Put the maven-war-plugin in the pom.xml file
5. Create another Maven project in the workspace with jar packaging (this will
be your dependency-- Project B)
6. Make Project A depend on Project B by adding Project B's groupId,
artifactId, and version in the dependencies section in pom.xml file for Project
A
7. Right click Project A -> Run -> Maven Build...
8. Configure then Run panel as you see in the screenshot.
9. Run
> war fails to build while using m2e in workspace resolution mode
> ---------------------------------------------------------------
>
> Key: MWAR-269
> URL: https://jira.codehaus.org/browse/MWAR-269
> Project: Maven 2.x WAR Plugin
> Issue Type: Improvement
> Affects Versions: 2.1.1
> Reporter: Chris Gamache
> Attachments: maven-war-plugin.patch, screenshot-1.png
>
>
> This is my first time for an issue/patch submission. Apologies if I'm doing
> it wrong....
> When building in Eclipse using m2e in workspace resolution mode, the
> maven-war-plugin is not prepared for a "dependency" which isn't an assembly
> but is instead a folder containing the compiled classes from within the local
> workspace. I propose that if the incoming dependency happens to be a
> directory that it get packaged up and copied to the destination instead of
> blowing up with an exception.
> See attached patch for your review...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
