Re: [M10N] When to ditch Ant and switch to Maven
Daniel Fagerstrom wrote: > * Still being able to use gump. IIRC, the maven boys have no intention of supporting Gump as of yet. If nothing else we'll have to craft something ourselves, or maintain gump.xml manually. Jorg
Re: [M10N] When to ditch Ant and switch to Maven
Jorg Heymans wrote: Daniel Fagerstrom wrote: * M2 stable enough (2.0 is out so this should be fullfilled) * Reasonably fast (don't need to be as fast as Ant, but not several times slower) * Easy configuration of what blocks to compile (like blocks.properties and maybe even dependency aware) * M2 bundled with Cocoon (it should still be enough to just download and type ./build.sh) I agree with above set, here are mine : (all mainly pom related) * produce jar artifacts from core and every block * produce jar artifacts from core samples and block samples * be able to run all tests Yes, would also like to add: * Still being able to use gump. /Daniel
Re: [M10N] When to ditch Ant and switch to Maven
Daniel Fagerstrom wrote: > > * M2 stable enough (2.0 is out so this should be fullfilled) > * Reasonably fast (don't need to be as fast as Ant, but not several > times slower) > * Easy configuration of what blocks to compile (like blocks.properties > and maybe even dependency aware) > * M2 bundled with Cocoon (it should still be enough to just download and > type ./build.sh) I agree with above set, here are mine : (all mainly pom related) * produce jar artifacts from core and every block * produce jar artifacts from core samples and block samples * be able to run all tests Jorg
Re: [M10N] When to ditch Ant and switch to Maven
Daniel Fagerstrom wrote: * M2 stable enough (2.0 is out so this should be fullfilled) * Reasonably fast (don't need to be as fast as Ant, but not several times slower) For me, this isn't an issue. * Easy configuration of what blocks to compile (like blocks.properties and maybe even dependency aware) ??? Compiling all the blocks is not the issue for me. block selection should happen at install time. However, I'm sure there are ways to exclude or include blocks at build time. * M2 bundled with Cocoon (it should still be enough to just download and type ./build.sh) Further rquirements? /Daniel
[M10N] When to ditch Ant and switch to Maven
was: [M10N] separating samples from blocks Jorg Heymans wrote: Another thing i didn't think of last night is that this will impact the current ant build of 2.2 as well. How easy is it to change this, just a matter of adjusting paths ? More importantly : how long should we still care about the Ant build in 2.2.x ? Until you or someone else cast a vote about ditching Ant and go for Maven At what point would people be happy to ditch it and go maven all the way? Essentially when the Maven build is "good enough". I haven't tried it or followed the development for a while, so maybe it allready is. IMO, the maven build doesn't need to replace every single Ant task we have, some of them can be reimplemented in Maven when someone have a strong enough itch. It'll become increasingly more difficult to keep both builds happy, and trying to do so might make a mess of both. I think we should gather a list of _minimal_ requirements that the maven build should support before we stop caring or even remove the ant build in 2.2. I'll start a new thread for this. You where not fast enough ;) * M2 stable enough (2.0 is out so this should be fullfilled) * Reasonably fast (don't need to be as fast as Ant, but not several times slower) * Easy configuration of what blocks to compile (like blocks.properties and maybe even dependency aware) * M2 bundled with Cocoon (it should still be enough to just download and type ./build.sh) Further rquirements? /Daniel
