On 5/26/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
There's probably an easier way, but I just create the elipse project for the
project I want to use, like let's say, core and showcase, doing:
core/
mvn eclipse:eclipse
apps/showcase/
mvn eclipse:eclipse -Dwtpversion=1.0
and then import the projects, if you do it like that, you need to compile
core with maven because the reference in the showcase project will be
pointing to the M2_REPO folder. To compile core(configure it to run as an
external tool):
That works for the showcase app. Wondering why the mvn
eclipse:eclipse goal will build the plugin projects' eclipse metadata
with a project dependency of struts2-core instead of core? Does this
have something to do with an assumption that you would have
struts1-core in the same workspace?
Sounds like reasonable fixes are: 1) change project dependency from
struts2-core to core or 2) change to M2_REPO dependency instead of
project dependency and use mvn build.
1) Worked for me.
2) M2_REPO dependency is implied, at this point.
https://issues.apache.org/struts/browse/WW-1947
core/
mvn -Dmaven.test.skip=true install
I think there is a way to have maven generate the projects with the
references between them for eclipse, but I'm not sure how, we can put it on
the wiki if someone replies :)
Would like to have some more info about how you setup the maven build.
I couldn't get this plugin <url: http://m2eclipse.codehaus.org/> to
play nice. Nor was I successfully able to add a "Program" builder to
my project.
-Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
