For what it's worth I second the ruby concern. Sure many developer
machines may (or may not) have ruby installed, but what about dedicated
build/test/integration boxes that build code? I'm not against better
tools, but even if maven has rough edges it has provided an easy
'language' for developers to speak when talking about dependencies, etc,
not to mention the transparent management of jar-hell.
If a change of this sort is going to happen, I'd which for these:
1. Focus on getting T5 out the door first, before further interest is
lost of more community splintering occurs.
2. Do not abandon publishing maven artifacts as many of us use maven
happily without using the troublesome parts, and our lives are made easier.
3. At least consider the impact of requiring yet another language
runtime to perform the builds. On a related note, I wonder if JRuby
could bridge the gap...
chris
Massimo Lusetti wrote:
The .apt doc format issue is a big one IMHO, plus force developers to
use ruby is not so friendly :)
