If you aren't using Maven day-to-day you may not realize what a huge pain it is, especially w.r.t. creating releases.
It also gets in the way of creating new subprojects. Maven is a sunk cost and you don't keep throwing resources at a sunk cost just because its cost you in the past. On Fri, Jan 7, 2011 at 1:44 PM, Robert Zeigler <[email protected]>wrote: > I haven't used gradle. I'm sure it's wonderful. I'm sure it beats the > heck out of using maven. > But. Do we really need to change build methodology /again/? We have a > build. It works. It's not always the nicest thing in the world to work > with*, but it works. People are familiar with it. Tools understand it. > It just seems like another barrier to getting users to contribute if they > have to install yet another piece of software. > > Just my $0.02. > > Robert > > * It can be made much more workable with a bit of shell scripting... > > > On Jan 7, 2011, at 1/73:32 PM , Howard Lewis Ship wrote: > > > I really want to take a crack at converting Tapestry to build using > Gradle. > > Does Hudson support Gradle yet? > > > > -- > > Howard M. Lewis Ship > > > > Creator of Apache Tapestry > > > > The source for Tapestry training, mentoring and support. Contact me to > learn > > how I can get you up and productive in Tapestry fast! > > > > (971) 678-5210 > > http://howardlewisship.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
