Re: maven.
Re: maven.
- Subject: Re: maven.
- From: Henrique Prange <email@hidden>
- Date: Mon, 06 Apr 2009 20:29:24 -0300
Hi Chuck,
Chuck Hill wrote:
Sure. If the solution is good, what is the problem of reusing it?
One problem that I would expect is that you can only be all things to
all people by addressing the lowest common denominator. So anything
unique in how I want to have things work is either fighting against the
Maven way or writing my own extensions to Maven or giving up and
accepting something less than perfect.
Fine. I'm not saying we should not seek "perfect" solutions, but "the
perfect is the enemy of the good".
Again, IMHO, you already have what you desire. Why are you so worried
about the Maven discussion? I'm just trying to provide information and
option to developers not satisfied with the current way they manage
projects. I never said people must use Maven. In fact, I have always
pointed out Ivy and Maven Ant Tasks as alternatives for those that just
want the dependency management thing.
How to handle the development lifecycle of interdependent projects.
Interdependent? You mean circular dependancies? Or just a dependancy
tree without cycles?
Maven doesn't not support circular dependencies. You have to get rid of
them because it is considered a bad practice.
From the inception to the continuous process of release and
maintenance. How you build, package, test, deploy, release, produce
documentation, produce reports and metrics and etc. In a way that not
only you, the guy that made the scripts, knows how to handle. In a way
that can be clear for other people too. In a way that other people can
easily use and contribute. In a way that a simple change in the
environment doesn't bring everything down.
A simple change like someone deleting something from their Maven
repository that you were depending on? That is not a theoretical
question, I ran into that exact problem trying to build an Open Source
project that used Maven. I had a lot of fun tracking that down and
working around it.
If you want any help, you know my e-mail. ;)
I started using Maven 3 years ago to manage WebObjects projects on my
company. We invested money and time along these years to improve the
way we develop software. Before this investment, every release was a
pain. We were not able to follow our schedules. Development was a
mess. It was very difficult to introduce new members in the middle of
a project. It was hard to define the quality of the code produced.
Resuming, we wast a lot of time.
Maven helps you meet schedules? I am finding that hard to believe.
Believe or not, I can't recall the number of times in the past we had
the development done and we can't delivery the final "product" at time
because of package or deployment problems.
We started to seek a way to reduce the waste of time. Maven solved all
the problems? No. We have also started to use other tools and
concepts, like Eclipse, Jira, Confluence, Hudson, Selenium, Scrum, TDD
and go on. Today Maven help us to perform lot of tasks we didn't have
idea about how to accomplish in the past. Is it perfect? Not at all.
But it is a invaluable piece on our environment.
That is a lot of changed tools and processes. It is hard to identify
which tool is responsible for what change.
I agree.
Out of steam.
Me too.
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: Chuck Hill <email@hidden>) |
| | >Re: maven. (From: Henrique Prange <email@hidden>) |
| | >Re: maven. (From: Chuck Hill <email@hidden>) |