maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Gamache (JIRA)" <>
Subject [jira] (MWAR-269) war fails to build while using m2e in workspace resolution mode
Date Mon, 11 Jun 2012 13:00:22 GMT


Chris Gamache commented on MWAR-269:

I don't think so, but I am no Maven expert.

The problem I was observing was an interaction in the war plugin plus m2e. In workspace resolution
mode, m2e is happy to provide a folder of classes instead of building a jar for a named artifact.
This is fine when you stay within the bounds of Eclipse for your program execution. If you
happen to want to build a war consisting of classes in the workspace using m2e you're out
of luck.

Taking a page from the way the assembly plugin handles this situation, the patch I proposed
would allow the war plugin to package the classes folder and add it to the war.
> war fails to build while using m2e in workspace resolution mode
> ---------------------------------------------------------------
>                 Key: MWAR-269
>                 URL:
>             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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message