Eclipse classpath variables don't solve the issue because each developer may be using different variable names. Further, the name of the jar file may be different (ie. have version number in it). In my experience, forcing developers to use the "one true setup" is a recipe for disaster.
This is off topic now so I'm sorry to continue it, but I'm not sure I get your point here.
Why would a developer use different variable names? If .classpath/.project for eclipse were included, there must be documentation saying "you must setup VARIABLEX to point to RESOURCEX" and so forth.
Are you worried that people won't read the documentation? Or that multiple variables may point to the same resource?
I also don't get why it matters that the name of the jar files may be different. That is the point of the variables. If I have variablex pointing to:
c:/matt/struts/libs/resource1.2.3.jar
and you have variablex pointing to:
c:/david/struts/libs/resourceABC.jar
it doesn't matter as far as I know. One of the developers here compiled his own copy of junit with some specialized stuff in it that I didn't know about for a long time, mostly because we use variables to point to the junit jar :)
I do think there would be problems with people forgetting to update a variable to point to the proper version of a resource...but your arguments aren't making sense to me.
Matt
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
