Re: maven.
Re: maven.
- Subject: Re: maven.
- From: Mike Schrag <email@hidden>
- Date: Fri, 3 Apr 2009 18:27:31 -0400
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. 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." I want people to launch WOLips and things just work.
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?
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.
ms
_______________________________________________
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>) |