This is the approach I took when we first moved EJB3 out, only I did not check in any
m2eclipse-specific files. Popular demand of developers outside EJB3 desired generated
Eclipse files in SCM. :)
It worked pretty well. m2eclipse will re-set your CP with every change to the POM, at the
cost of some added compilation time.
Scott, the generated artifacts are proprietary lines in .project and .classpath, so upon
creation of a new project I'd strip these before commit, and then leave 'em
untouched.
I say let each developer be responsible for import of the project into his/her own
preferred IDE.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146798#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...