Alex, Niclas, I'm forced to agree that using maven can feel really cumbersome sometimes :) I must say I like it anyway.
I'm not a maven developper, only a sort of "power user" and like Alex it is really hard to keep myself from talking about this when the subject is re- producible maven builds :) Maven comes with default plugins versions so that you can quick-start without worrying. As soon as you ask for re-producibility you have to specify the plugins versions you're using so in the future the very same are used. I have projects set up two years ago that never suffered from this. But yet again, all this is a bit cumbersome. The plans for maven 3 are interesting. Some things I noticed and think can really decrease all this cumbersomeness : - use of a boolean solver for dependencies resolution - pom mixins (!!) - ruby, groovy, python DSLs for writing poms - tagging in poms If the qi4j builds have reproducibility issues I could give a hand. /Paul Le mardi 12 mai 2009 20:35:13, Niclas Hedhman a écrit : > On Tue, May 12, 2009 at 7:59 PM, Alex Shneyderman > > <[email protected]> wrote: > >> Well, personally I am open to suggestions for something that provides > >> more value, and the hands to make it happen. ;-) > > > > ATM, I am just bitching. It is really hard to keep myself from doing > > this when the subject has maven in it. The biggest problem with maven > > for me is re-producible builds. I still can not build the libraries > > from source (hence can not use native rdf indexing) - although this > > might not be maven's fault or it might ... and this is exactly my > > point if ant were used to build I would never be able to be in doubt. > > If nothing else works, this should. If not, please send me the output > on a "mvn -X install" of the part that fails. > > rm -rf ~/.m2/repository > cd qi4j-core > mvn install > cd ../qi4j-libraries > mvn install > cd ../qi4j-extensions > mvn install > > > Aside from that I am waiting for gradle to become a bit more stable > > and functional. Then I could come up with suggestions for alternatives > > and hands. > > I have looked at Gradle, and spent several days with Hans Dokter (at a > DDD training). IMHO, Gradle seems to fail in similar fashion of Ant, > but doing so with a friendlier syntax. I think that the field is still > wide-open for a Rules-Engine based build system, modular like Maven, > dependency handling like Ivy and a friendly syntax like Gradle. On top > of that, it would need to deal with SCM abstractions, publishing > channels (SSH,FTP,++), Licensing tracking, customizable workflows and > heaps of other complex matters. I *think* that Ant, Grails, Maven and > what not, are not taking a holistic approach to the entire domain of > software engineering workflow. OTOH, I suspect that many commercial > ones have done so, and instead stuffed a dead rat down the throats of > developers, i.e. something too complex to be productive. > > Heard on the grapevine is that Maven is to be refurbished with OSGi > under the hood (instead of Plexus), and hopefully in that larger > effort perhaps some new workflow related features appears as well. > > > Cheers _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
