On Mie, 23 de Febrero de 2005, 9:43, Ralph Goers dijo: > Reinhard Poetz wrote: > >> >> Mark asked me about my vision about blocks. Well, I think, its very >> close to that what Stefano proposed 18 month ago. >> >> - A block is a service provider (components, pipelines, flowscripts) >> that other blocks can use. >> - Blocks can depend on other blocks (use or extend them) >> - starting your Cocoon based project is done as a block >> - the general behavior of a block is described at a _single_ place >> (block descriptor) >> - a very lean Cocoon core (only pipeline and flow stuff) >> >> As you can see, my vision has nothing to do with Maven, Ant or any >> other build tool. Personally, I like Ant more because *I* understand >> it and I know exactly what it is doing. *My* personal experience is, >> that whenever I used Maven, I ran into problems and it took me ages to >> get things going. Probably my personal stupidity :-) Two other reason >> for me : Since Ant 1.6 reusability (import and macro) is possible >> (it's not true any more that you have to write your Ant scripts over >> and over again) and that nearly everybody is able to read and write >> Ant himself. >> >> Hence I went for Ant. Writing an XSLT that transforms the block.xml >> into an Ant script wasn't very difficult and the best solution *for me*. >> >> If somebody can show a (better?/another) solution using Maven, we have >> a whiteboard. It can be used to setup the ideal environment for Maven >> and we can decide whether we think the required changes are good or >> not. The only requirement I have is, that block.xml should be used to >> drive the build but it was shown that this isn't a problem at all. > > I'm in total agreement with this. The main difference is, that anything > you can do with ant you can also do with maven since ant is an integral > part of it.
please see: http://jroller.com/page/carlossg/20050221#hibernate_vs_jdbc_maven_vs Best Regards, Antonio Gallardo.
