"alesj" wrote : OK, I definitely don't want to see you loosing too much time
doing this stuff :-), but I fail to see how this is relevant.
|
| e.g. you get your updated .classpath from svn
| or you get updated pom from svn, close Eclispe (so you're not pulling the rug),
run the maven-ide generator, open Eclipse
|
Because, I get an error when I load eclipse when it can't find the method/class/jar.
I fix it, and then I've might have to fight eclipse's incremental compiler
because I missed a step in some many stage svn update procedure.
We've had this discussion before. What I really want is maven to automatically
run mvn eclipse:eclipse when it detects the .classpath is earlier than
the pom.xml. That way any developer modifying the poms will
automatically check in updated .classpath files and it doesn't become
an "infinite stage" process to get a working development environment
after an svn update as I try to figure out what changed
what I need/forgot to rerun and what eclipse thinks is going on.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133278#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...