On Feb 12, 2008 11:16 AM, Christian Edward Gruber <[EMAIL PROTECTED]> wrote: > True. You can always stop using maven. My problem with that (purely > in my own experience) is that it replace the gawd-aweful 50K-worth-of- > ant-scripts/make-files I've inherited. The notion of a stable > lifecycle (even if I have to do more work to lock down the plugins) > ends up being more than worth it. But that's my own situation. Your > mileage may vary. Given that they're working out some issues at the > core, I guess the next step after that is to work out quality in the > plugins themselves. > > Anyway, I guess this has really strayed OT. Sorry. It's just after > having built build system after build system in *make/jam/ant, and > seen the crap that ends up accumulating in corporate builds at my > clients, Maven still seems the cleanest way to get to reproducible AND > manageable builds. Sad though that may sound.
I've had my fill of Maven and am anxious to move away from it. Creating a good build is a difficult challenge for most developers. I think the majority of devs who take a crack at a build system are handicapped by not knowing what they don't know. An experienced dev can leverage the Maven Ant tools or Ivy and create a better bulid than Maven and that's the direction I intend to go in the future. > > Christian. > > On 12-Feb-08, at 13:33 , Jesse Kuhnert wrote: > > > I know what will make it stop though. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
