I agree - nothing wrong with competition. But, at least for this discussion - who cares if it is a young project or not for a build tool? This is not something that is built-in to JSecurity, i.e. something required for the framework to function. The only risk we undertake is that the project might die, in which case we switch do a different build system. It is not like our end-users would even notice.
Part of why I enjoy open source is that we can engage in cutting edge frameworks and tools and approaches that I often can't indulge in with corporate projects. It allows us to vet these things in a fun and creative environment. In this particular case, if we didn't like Gradle or Buildr, or whatever, the worst thing that happens is that we just delete those 2 or 3 build files and revert to the ant files. Seems like a very low risk to me to try something fun out... Cheers, Les On Sat, Dec 27, 2008 at 12:02 PM, Alan D. Cabrera <[email protected]> wrote: > > On Dec 26, 2008, at 4:14 PM, Emmanuel Lecharny wrote: > >> Les Hazlewood wrote: >>> >>> Nope, none at all - I was just bringing it up for discussion to see if >>> people wanted to give it a go. I found it enjoyable and was thinking >>> others might as well. >>> >> I think that it's better to get close to what people are used to. I would >> rather favor a move to maven, if we decide to change the build system, as >> it's more likely to be a build system people know, and it has proved to be >> stable, reliable and capable of handling quite complex build. >> >> Gradle, IMHO, sounds like the last hype... > > May not be hype. I've always had the philosophy of letting a thousand > flowers bloom. It's just that this project just got started. > > > Regards, > Alan > >
