Re: WebObjects Nightly Builds and WOLips addition
Re: WebObjects Nightly Builds and WOLips addition
- Subject: Re: WebObjects Nightly Builds and WOLips addition
- From: Lachlan Deck <email@hidden>
- Date: Fri, 13 Jun 2008 06:59:11 +1000
On 12/06/2008, at 6:51 PM, Andrus Adamchik wrote:
On Jun 12, 2008, at 4:34 AM, Chuck Hill wrote:
My question was more of this: I already keep my dependancies (as
deployed) in svn. So I don't have any fear of them being
unavailable in the future. Given that (and that I am comfortable
with the implications of that as I understand them), what
advantages does Maven offer me. I am willing to be convinced. I
just don't "get" Maven yet. And I have had a few, er, run ins with
it. What am I missing?
The whole thing about jars in SVN vs. in the repo is so typical of
Maven - it is a nice idea in an ideal world, in reality it is a pain.
Yep. I understand the concept. They harp on about being built on best-
practices... but I've not found the spec yet ;-)
It would not be hard for maven to do, however, given its current
definitions: just allow the systemPath to be used for more than the
system scope.
But I found ant a real pain also.
Every time you start getting fancy with your deps, you POM's
explodes with special rules excluding/fixing transitive
dependencies, etc.
Sounds like ant too :-)
There are other genuinely good ideas. But IMO *all* of them are
coupled with bad usability, just like the one above. Here is a few
examples:
1. Project Descriptor. Build system done around a source tree model
is great. Take Eclipse .classpath/.project for instance. In case of
Maven this would be pom.xml. I like this approach. Model opens up
your source tree to any number of build, analysis and reporting
tools (even things outside of Maven plugin zoo, such as Ant Ivy can
use the POMs). Now the XML format itself makes you want to cry. All
tags and no attributes approach results in a sparse huge XML
documents that are barely human-readable.
There may well be better xml formatting, but FWIW I personally
wouldn't paint it quite so glumly. At least, it seems quite readable
to me (i.e., there's a set of available options for each element as
defined in the model). But perhaps I've not seen the examples you're
thinking of.
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden