> [jar hell]
There's little that can be done in such a case
.Net pulls it off IMVHO. Aside from the default settings of visual studio (spit), I think they pretty much figured something workable out.
I was thinking about ways to keep it from happening.
I think any kind of versioning scheme will still not be able to "enforce" enough rigidity, lest it become too much of a pain. I think what is much more valuable is solid integration testing (gump!).
The above could be made into an Ant task.
the algorithm is nice, and makes sense. It seems like this could be a valuable reporting tool. But I'm a little scared because of the "automatic"...just some thoughts ;)
-- cheers,
- Leo Simons
----------------------------------------------------------------------- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles & Opinions -- http://articles.leosimons.com/ ----------------------------------------------------------------------- "We started off trying to set up a small anarchist community, but people wouldn't obey the rules." -- Alan Bennett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
