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.

Reply via email to