"adrian(a)jboss.org" wrote : We'll continue to disagree.
I'm OK with that. :) But I would like to come to a conclusion here (one way or the
other) as I'm sometimes unsure how to best maintain my projects' builds.
"adrian(a)jboss.org" wrote : It's called an I(ntegrated)DE for a reason
...so we should account for Eclipse's shortcomings in the repo?
"adrian(a)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.
"adrian(a)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.
"adrian(a)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.
Exactly! I'm banking on "not everyone updating", meaning you'd have to
run eclipse:eclipse anyway. The difference is one of precedent; by not committing
.classpath you EXPECT to have to make this step, not wondering why the build is broken.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133314#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...