Re: maven.
Re: maven.
- Subject: Re: maven.
- From: Lachlan Deck <email@hidden>
- Date: Sat, 4 Apr 2009 12:19:53 +1100
On 04/04/2009, at 9:27 AM, Mike Schrag wrote:
Perhaps you're forgetting the reason why you went to great lengths
to rewrite (more than once?) the build system for wolips. But
perhaps it wasn't a pain for you but a joy writing a new build
system. The switch env scipts, the [wolips|wobuild].properties,
dealing with multiple versions of dependencies and so on... and the
ongoing support requests.
No, I remember quite clearly why I wrote it, and that's because I
wanted the users of WOLips to have a very simple experience out-of-
the-box, and Maven does NOT provide that.
That all depends on what you mean by out of the box. Both build
systems rely on WebObjects being installed.
Beyond that what out of the box are you referring to? Even now on the
mailing list there's constant questions about how do achieve things
with the current build process. I'm not suggesting this is your fault,
but it's not all plain sailing 'tis all I'm saying.
Creating a simple project is easy in both systems is my suggestion.
Adding project dependencies IMHO is easier with maven.
Granted, the onus is on us to do better with the wiki.
I can't say "oh you want to build and test your app -- sure learn
maven -- here's the name of the book to start."
Nor do you need to.
I want people to launch WOLips and things just work.
Sure. The reason why this doesn't currently work out of the box for
maven-based apps is to do with WO's need for bundles. We (the maven
dudes) are already talking through this. Should be simple.
I hate (*HATE*) build systems. They all suck. I don't want to
think about a build system. I want it to just work. If you want
something fancy, learn Maven and go crazy. If you want to instead
agree to our requirements, then you do nothing and WOLips "just
works." As I understand it, even when you use the Maven plugins and
build system, to launch your app you still have to use our
incremental builders if you want hot code replacement?
We're currently using the wolips incremental builder in addition to
the maven one yes. The solution to the above problem will either
involve not using the wolips incremental builder or using a simply
config change to build into compatible dirs. Daryl, for example, uses
a slightly different config that seems to work for him.
We also don't like things the way they are. We're working on a solution.
Still now in a shared environment it relies on users systems,
intranet build systems having the same installed frameworks rather
than centralised and auto-downloaded etc. What if you want to roll
back to a specific version of wonder etc? Does that happen
automatically on every system by a simple declaration of a
property? It's easy for me to install a central release of wonder,
for example, update the master pom with that version, commit to svn
and everyone else gets it by virtue of an svn up.
I've always said that Maven supports dependency management that the
others don't. I've never said Maven is *useless*, rather that, for
the problems I have, it seems far to complex. That said, I have
never felt like dependencies was really THAT big of a deal for me.
We have a set of dependencies we rely on and those are in
frameworks. It's not perfect. It has flaws. But it's easy. And
when something goes wrong, it's pretty easy to fix. I've never
rolled back a version of Wonder, but then having commit access maybe
makes that an easier problem to solve :) I would like to have
autobuilding dependencies and project dependencies that dynamically
build, yes, but do I want to trade that for Maven ...... still not
feeling it.
You haven't described the problem you're trying to solve...
dependencies are easy in both systems (though I believe it's easier in
maven - but that's besides the point). You haven't started this whole
thread for curiosities sake. Let's, for arguments sake, assume you've
started working on a project that's currently using maven and that
this is the reason for your posts and you're perhaps considering
whether or not to migrate said projects back from maven to ant ... I
want to know why.
What problem are you having?
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
| References: | |
| | >maven. (From: Mike Schrag <email@hidden>) |
| | >Re: maven. (From: Henrique Prange <email@hidden>) |
| | >Re: maven. (From: Mike Schrag <email@hidden>) |
| | >Re: maven. (From: Lachlan Deck <email@hidden>) |
| | >Re: maven. (From: Mike Schrag <email@hidden>) |