[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Update the relevant .classpath files

[adrian@jboss.org]

"ALRubinger" wrote : 
  | "adrian at jboss.org" wrote : Remembering and performing recipes of many tool procedures is not productive
  | 
  | You're going to have to do it anyway whenever you make changes to the dependencies.
  | 

Not if there's a mojo defined in the pom that says, aha the pom is newer
than the .classpath file, re-run eclipse:eclipse automagically.

"adrian at jboss.org" wrote : Redundancy is only a problem when it leads to error or reduced performance

This is the root of my concern; an Eclipse user with an outdated classpath.


How is it different to what you suggest (no .classpath file or an old
one they generated before doing the svn update?)

"adrian at jboss.org" wrote : Checking in the eclipse files in svn makes little difference in practice unless everybody updates them you have to run mvn eclipse:eclipse anyway. 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133318#4133318

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133318