[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] m2e-ifying maven plugins
|
Let me attempt to make my case:
m2e-wtp works fine for running a web app inside the workspace. m2e-wtp has no problem publishing the artifacts found using workspace resolution mode. Sometimes I find it necessary to package a snapshot WAR from artifacts found when resolving workspace artifacts to run outside of the workspace environment.
There is an option in the Maven run dialog to resolve workspace artifacts. This causes m2e to provide the workspace artifact's target/classes to be packaged into the war instead of an already packaged artifact for further packaging.
If I recall correctly, the maven-assembly-plugin responds properly to recieving a folder tree of classes instead of a packaged artifact when it goes to package a jar. This patch extends the same functionality to the maven-war-plugin.
On Fri, Mar 9, 2012 at 11:10 AM, Jason van Zyl
<jason@xxxxxxxxxxxx> wrote:
Why not just use m2e-webby or m2e-wtp. Both provide workspace resolution. The Maven WAR plugin is for packaging which doesn't really play a part inside the workspace. You generally wouldn't package a WAR file in Eclipse. I'm curious why you need to do this? I honestly don't think that patch to the Maven WAR plugin makes sense at first blush. I honestly don't understand the use case.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
A language that doesn’t affect the way you think about programming is not worth knowing.
-— Alan Perlis
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
