> How interesting, quite a few projects have managed to do it. Obviously we are far less competent, intelligent, or dedicated then those other projects. All things I am perfectly willing to accept as long as you don't make me look at GUMP again.
> more than it costs. Say I want to use Maven, but one of its > dependencies turns out to be incompatible with something I'm using in my > project. I think despite the really nice documentation that I'll find > it a bigger pain if I can't use a version of a library that I want Just to clarify for the general audience, Maven does not introduce any of its dependencies into the classpath for a project it is building, thus there should be noe problems of this sort. Maven also allows your project to specify dependencies on a specific version of another project without trouble. There are still some kinks to work out with the repository and naming and auto downloading and such, but none of what is outlined here _should_ be a problem. > http://www.martinfowler.com/articles/continuousIntegration.html Yes! All of us over in maven land are big fans of continuous integration. We were in discussion with the cruise control folks about working together, and are planning on integrating the best features from it into maven so that any project with a descriptor can immediately be set of for continuous integration (since maven supports version control and unit/integration tests out of the box, this is going to be quite easy (and fun!) to implement. -- jt -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
