I suspect this is a bug in Eclipse, not maven, but I wanted to see if anyone 
else had experienced it.  
 
I have two projects in Eclipse, and one (project B) depends on the other 
(project A).  I ran 'mvn eclipse:eclipse' for both and have my classpath set to 
depend on the M2_REPO.  
 
I tried making a change to project A that should cause project B to no longer 
compile.  When I ran 'mvn install' via an External Tool launcher in Eclipse, 
with the "Refresh everything" option turned on, project B did not appear to 
refresh and still indicated that it compiled.  Hitting F5 on Project B caused 
it to refresh and indicate the compile error properly.  
 
I've had success with the "Refresh Everything" option and Ant builds before, so 
I'm somewhat surprised it's not working here.  Can anyone else comment?
 
K.C.

Reply via email to