Re: maven.
Re: maven.
- Subject: Re: maven.
- From: Henrique Prange <email@hidden>
- Date: Fri, 03 Apr 2009 22:02:21 -0300
Hi Mike,
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.
What problems do you see? Could we improve the tool to better fit your
needs? Which specific problems are you facing?
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."
But couldn't you say: "Do you want to improve the entire development
lifecycle of your projects? Do you want to improve the way you MANAGE
your projects? Here is a tool and the name of a book to start. And you
don't have to read the entire book to recognize the benefits".
I want people to launch WOLips and things just work.
So you want something that works only for WebObjects projects? For me
this a huge drawback, for example.
I understand you see a problem on WOLips+Ant implementation, right? You
want to improve it, but you think it is to much to ask people to add a
set of tools just to have more control over their environment, correct?
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."
Would you mind being more specific? Your proposal is very similar to the
concepts behind Maven. If you agree with some requirements, Maven just
works and does everything for you. The only difference is that your
solution will work only for WebObjects projects.
BTW, Maven have a few commands to solve most of your problems. Those
commands are the same for every project in the world that uses Maven.
Most configuration you have to do in a project after its creation is to
add/remove dependencies. And you don't have to manipulate XML with the
new POM editor from m2eclipse. Where is all the complexity? Does the
number of tools required to make all the environment ready make you crazy?
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?
Yes. Is this a problem?
Cheers,
Henrique
_______________________________________________
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>) |