Re: [Springframework-developer] RE: commons-validator adapter

[Seth L. <se...@eh...>]

> you. XDoclet has 10million dependencies (ok.. I exaggerate.. 999,999 
> dependencies) and most of them are broken which results in a XDoclet2 
> that does not build out of CVS. VERY VERY aggrevating.
> Can I make a suggestion and vote to take a page from Maven's book?
> Let's create a Spring-Plugin project of these "add-ons" they never have 
> to get mixed with the main code and the main code will NEVER have to 
> break due to breakages in the plugin's dependencies.

That's a great point, and which is why I never build against CVS. 
Here's where maven is nice: it let's you specify a particular version of 
a jar as a dependency and then your project is stuck with that.  You 
become immune to all the new versions of that jar (which can be very 
dangerous).  If you're not using maven, you could just capture any jars 
needed for compilation/runtime and check them into your project's source 
control.  The same effect is achieved: locking into a version of a 
dependency.

So far, the Spring developers have done a great job in not introducing 
any code into the source tree that would jeopardize the integrity of the 
project or the build process.  Many, including myself, view Spring as 
production ready code and not a playground (which is how I view 
xdoclet2, for instance).  I trust the Spring developers to Do The Right 
Thing.

Seth

ps OK, I've got to be quiet now and get some work done. :)