Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <27666958.post@talk.nabble.com>
Date: Sat, 20 Feb 2010 07:56:34 -0800 (PST)
From: tbee <tbee@tbee.org>
To: dev@maven.apache.org
Subject: Re: custom maven plugin default phase
In-Reply-To: <28B6315D-0114-4030-8683-5FEA7C6B4A67@sonatype.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <27626122.post@talk.nabble.com>
 <20FC2CC6-6970-4BAE-A4E5-526CA0470D7D@coremedia.com>
 <88c1b41002190025y31c7f2fdm6995ad470b6bf84e@mail.gmail.com>
 <27651482.post@talk.nabble.com>
 <88c1b41002190405u263edb76l7fd9252c37fa1ccf@mail.gmail.com>
 <27657303.post@talk.nabble.com>
 <88c1b41002190953u6d41c85bwd63efe94f892c463@mail.gmail.com>
 <27658340.post@talk.nabble.com>
 <C31CDB65-B82B-41D0-A3A6-AEC29231D27E@sonatype.com>
 <27664065.post@talk.nabble.com>
 <28B6315D-0114-4030-8683-5FEA7C6B4A67@sonatype.com>


jvanzyl wrote:
> 
> Most people we deal don't actually find that, it's usually not understand
> the tool and the impatient find it easier to roll their own solution.
> 

During my research I found many developers of well know open source projects
tried and failed migrating to Maven. After all that is why Ivy came to be,
and Gradle and all the other Maven derivates. If there is smoke, then there
is a fire. It can't be that all these developers are too impatient. Hell,
I'm on this migration thing for about 3 months now. Maven simply is fairly
complex; I'm busy migrating our medium sized projects and after three months
I'm still fine tuning. And my first attempt at a custom plugin immediately
runs into difficulties immediatly.

One observation; in ANT I tell my build system how to go from A to Z. If I
look at my pom file, I do not see the "A to Z" , but I see almost every step
configured. I see A, libraries, because I want a copy for the EDI. I see B,
compiling, because I have to specify the source version, etc. So even though
the build script does not contain the exact sequence, it in core pom.xml
contains the same information as build.xml.

The Maven concept is good, don't misunderstand me, but at the moment it is
too much EJB2 and not enough EJB3, as a metaphore. If you guys are able to
do two things for Maven 3:
- make it easy to extend or override behavior, add easy plugins including
default behavior (looping back to the origin of this thread)
- make the configuration more compact

Then things should be quite different.


jvanzyl wrote:
> 
> So you can either help fix the lacking implementation, or roll something
> no one else in the world is going to understand. 
> 

You make a compelling point. But considering the knowledge gap between you,
the developers of Maven, and me, that is too idealistic. I simply do not
pretend to have the knowledge to make enterprise level design decisions on
this. My projects are medium in size. But if you guys can make a good rack,
then I most certainly can put the jackets on.

Can I try the Maven 3 feature already?
-- 
View this message in context: http://old.nabble.com/custom-maven-plugin-default-phase-tp27626122p27666958.html
Sent from the Maven Developers mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org