I'm using the m2eclipse plugin and I find it frustrating as well,
since I'm working with a lot of multi-module projects. One possibility
for easing the pain in the meantime would be to add an m2 build to each
project which performs the source:jar and install:install goals. This
should ensure that each time you build a project in eclipse it updates
the local repository jar to which other eclipse projects are referring.
Its not an ideal situation but it might serve to hold you over till the
project resolution bug is fixed.
Brad Davis
Chris Hilton wrote:
Believe me, I'm in no danger of wanting to ditch Maven, but I've got a
team of 30 or so developers to keep happy and they need to believe it's
worth it. We have a large number of projects and Maven's big selling
point has been that by using Maven's dependency resolution, we've been
able to reduce the number of projects that a developer has to keep
checked out in order to build a product, resulting in faster build
times. Part of having that project not checked out means that Eclipse
needs to have a way to resolve dependencies on those missing projects,
which m2eclipse gloriously provides. But because of MNGECLIPSE-59,
inter-project dependencies when a developer DOES have the projects
checked out are broken; you end up referring to the artifact in your
local repository and not to the locally checked-out project.
Now this is (apparently) all fixed up in 0.0.10 and I know we're all
impatiently waiting for Maven 2.0.5 so that 0.0.10 can go out the door,
but I'm hoping someone has managed to get some sort of interim 0.0.10
solution going that I can use to tide my team over with.
Chris
-----Original Message-----
From: Barrie Treloar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 29 November, 2006 18:31
To: [email protected]
Subject: Re: [m2eclipse-user] RE: Built Maven 2.0.5 to fix
MNG-1908, but Eclipse plugin uses 2.0.4.
On 11/30/06, Chris Hilton <[EMAIL PROTECTED]> wrote:
[del]
Not having direct resolution to locally checked out projects is
killing our development team and we're in danger of
ditching m2eclipse
altogether (which won't look good for our use of Maven either).
[del]
Chris, I have been lurching on this mailing list since
reasonably early on. I still don't use m2eclipse.
You can successfully use maven without m2eclipse, it is just
a very big nice to have.
Not having a working m2eclipse would not cause me to also ditch maven.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
