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: Thu, 12 Jun 2008 07:50:26 +1000
Hi Quinton,
On 11/06/2008, at 7:59 PM, Q wrote:
On 11/06/2008, at 5:59 PM, Lachlan Deck wrote:
Yeah, it's worth saying that you don't want to 'switch' blindly.
I spent a few months reading and kicking the tyres. It's one of
those things you really need to read up on to see if it works for
you.
So are you currently using Maven for real?
Yes.
I like the idea of maven, but my gut feel is that it's going to work
for me *most* of the time.
(precursor: I certainly don't have as much maven experience as either
Henrique or Andrus) but it's worth saying I'd recommend doing a lot of
reading so as to determine if such cases mean its a total no go. There
is no perfect build environment. Ant sux too.
I found, for what it's worth, that maven is something you want to do a
lot of reading on (see links previously provided) in order to
understand the what/why of maven. It's not Ant and you'll face an
uphill battle if you try to make it work like Ant. Understanding the
what's and the why's helps for the common cases.
For the cases where you've got some custom build logic that you need,
and if one of the existing plugins doesn't do it for you, you can call
ant from maven during any of the lifecycle phases to do some custom
stuff. I've not needed that yet.
The maven user list is very helpful for answering any questions. So
when docs are lacking that's the place to turn to (like this list is
for WO).
However one of those times I need to do something a little different
from normal I am going to wish I never decided to use it, and end up
fighting with it to the death. Initial impressions are that it does
what it's intended to do especially well, but doesn't appear to have
the same degree of intuitive configurability as ant.
Ant's a fine tool for various things - but I was getting frustrated
with it for a number of things, even starting to write my own plugins
to get it to do something that should have been trivial. I wasn't
keen, going forward, on the woswitch stuff and how that would work for
remote build servers or other developers or simultaneous project
development etc.
It also seems that you can use it without really needing to know a
lot about how it works, but if something doesn't go wrong, there is
quite a bit to learn to fix it.
Yep. That's a good caution. As mentioned, it does take some reading to
understand what options are available. Sure you can read someone
else's pom file and it'll oftentimes make sense (as it's quite
readable) BUT when you want to do something yourself you really need
the vocab in mind or the mailing list for tips.
I don't want to give the impression that using (or, as some would call
it, switching to) maven will 'solve all your problems' or that it's
'the only sane choice'. The cautions for using maven ought to be taken
into account - but it's also worth saying that the current ant
environment for WO is less than ideal. That was the motivation for me
for having a look around and as I mentioned it was no snap decision.
So don't go rushing into it... I guess for WO this is reasonably new
and so there'll be some kinks to iron out in terms of how WOLips works
with it.
These are just my impressions from several close encounters, they
may turn out to be unfounded.
I guess time will tell :-)
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