On Sun September 27 2009 5:37:24 pm Jason van Zyl wrote:
> On 2009-09-27, at 2:08 PM, Roland Asmann wrote:
> > Again, the way we work DOES have real workspace resolution. The
> > maven-eclipse-plugin makes the projects in the reactor reference each
> > other PER DEFAULT, and any other projects in the workspace if you
> > tell it
> > to.
>
> I just ran it on a project and that's not what it did. I'm not talking
> only about multi-module projects but other projects you may refer to.
> I'm often working on several related projects where I need to work
> with them all at the same time.
>
> > I'm not trying to tell anybody not to use M2Eclipse or anything, I
> > just
> > want to state that it is not correct to say that you can't use the
> > plugin
> > if you want workspace resolution.
>
> For inter-project resolution it is. For intra-project (i.e. multi-
> module) is does.
The maven-eclipse-plugin does a great job of wiring inter-project things
together. If someone files a bug report with a maven based test case, it's
great cause I just need to do "mvn eclipse:eclipse" and it's all wired up to
the projects I already have in my workspace so debugging is quick and easy.
That said, you DO need to tell it where your workspace is. You can use the
-D flag on the command line if you want. For me, I added a activeProfile to
my settings.xml:
<activeProfiles>
<activeProfile>extra</activeProfile>
</activeProfiles>
<profile>
<id>extra</id>
<properties>
<eclipse.workspace>/home/dkulp/working/workspace</eclipse.workspace>
</properties>
</profile>
So that the workspace location is always set and eclipse:eclipse can always
find it.
--
Daniel Kulp
[email protected]
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
