[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: What's a "trunk" good for? (apart from eating peanuts)

From: B. Smith-Mannschott <benpsm_at_gmail.com>
Date: 2007-01-14 21:57:29 CET

On Jan 14, 2007, at 21:00, korebantic wrote:

> Just curious -- why the need to mirror an eclipse project with an
> equivalent maven project? My limited experience with maven and
> eclipse seems to indicate that you can get maven and eclipse to
> play together (somewhat).

You're correct. There is a maven plugin which will generate an
eclipse project from maven sources. There are a few issues though
that have prevented this from taking hold thus far (mostly it's just
"inertia"):

- We started using just eclipse. We didn't implement automated
building until later.

- We're not yet very experienced with maven (see also point 1). And
only 2 of the 7 active developers have used the tool. In fact, I
think the state of our automated build is about as much theory as
practice right now. There's still some stuff we build "by hand" (with
eclipse) because we can't get maven to help us. (Sometimes I glumly
wonder if there's not something to be said for sticking with ant, oh
well.)

- It's simply easier to check out a finished, working eclipse project
than to expect each developer to fire up some maven incantations in
order to begin working.

- I'm, as yet, unsure which versions the of eclipse the maven task
supports. Since we run a mix of Rational Software Modeller (Eclipse
3.0), Eclipse 3.1 and Eclipse 3.2, I've held off on advocating going
the maven->eclipse route until the tooling becomes more stable.

// ben

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jan 14 21:57:52 2007

This is an archived mail posted to the Subversion Users mailing list.