This isn't working for me. I've been running it from the root directory (the one containing the master pom). It definitely does a reactor build, but the generated projects have no entries in the Projects tab of the Java Build Path screen of the project properties.
Looking at the code for the eclipse plugin, I don't see where it would actually create the project links. Can you point me at it or otherwise suggest what I might be doing wrong? K.C. -----Original Message----- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Friday, March 17, 2006 10:18 AM To: Maven Users List Subject: Re: [m2] Should eclipse:eclipse be generating project links? Yup it should work, just make sure you run eclipse:eclipse on the master pom because it won't work if you execute it on a children project. On 3/17/06, KC Baltz <[EMAIL PROTECTED]> wrote: > I have a multi-module project setup in the classic fashion: > > master pom > | > ---A > ---B > ---C > > Where projects A, B, and C have the Master as a parent and C depends on B and > A. Is the eclipe:eclipse plugin supposed to be configuring my Eclipse > projects with projects A and B on the classpath of C? It's not doing it for > me now, but I'm hoping I'm just doing something wrong. > > My goal is to be able to make changes to A or B and not have to do the full > 'mvn clean install' cycle every time. I can put the project on the > classpath manually, but then I'll also have to remove the M2_REPO reference > for that project every time I run eclipse:eclipse. > > K.C. > > -- Alexandre Poitras Québec, Canada --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
