On Jan 15, 2011, at 6:49 AM, Lachlan Deck wrote: > On 15/01/2011, at 2:12 PM, Mike Schrag wrote: > >> I'm all for Q's approach, too. For me, Ivy is the part of Maven that isn't >> so bad. You get the dependency management without all the other stuff on top. > > And, of course, you can interpret 'all the other stuff on top' in one of two > ways: > a) negatively, which seems to be the way this particular community keeps the > myth going that it'll be too much pain. (Perhaps certain people have a > hang-over from maven 1?). > b) positively, as meaning all the additional benefits maven provides and with > less pain overall. > > I found the latter to be true. :) Having everything is configured in your pom > file(s) and thus in version control (rather than requiring external configs > on differing environments), dependency management, proper build lifecycles > (with testing, integration testing etc), convention over configuration, lots > of handy plugins easily adapted. It's definitely worth a serious look. > > with regards, > - > > Lachlan Deck
If I had to describe Jenkins(Hudson) in a sentence, I would say: A webapp for automating builds that is similar to Apple's Automator. Can a Maven fan concisely describe Maven in something the size of a tweet so that I might understand why I would want to use it? For me, the problem isn't a negative perception.... I simply have no idea what Maven does or why I would want to use it. Thanks, Ramsey _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
