Return-Path: 
 <m2-dev-return-1970-apmail-maven-m2-dev-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-m2-dev-archive@www.apache.org
Received: (qmail 30809 invoked from network); 6 Jan 2005 12:00:42 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 6 Jan 2005 12:00:42 -0000
Received: (qmail 75905 invoked by uid 500); 6 Jan 2005 12:00:42 -0000
Delivered-To: apmail-maven-m2-dev-archive@maven.apache.org
Received: (qmail 75857 invoked by uid 500); 6 Jan 2005 12:00:42 -0000
Mailing-List: contact m2-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:m2-dev-help@maven.apache.org>
list-unsubscribe: <mailto:m2-dev-unsubscribe@maven.apache.org>
list-post: <mailto:m2-dev@maven.apache.org>
List-Id: "Maven 2 Developers List" <m2-dev.maven.apache.org>
Reply-To: "Maven 2 Developers List" <m2-dev@maven.apache.org>
Delivered-To: mailing list m2-dev@maven.apache.org
Received: (qmail 75843 invoked by uid 99); 6 Jan 2005 12:00:42 -0000
X-ASF-Spam-Status: No, hits=0.1 required=10.0
	tests=FORGED_RCVD_HELO
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from smtp.imtf.ch (HELO imtfinter.imtf.ch) (194.209.33.5)
  by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 06 Jan 2005 04:00:40 -0800
Received: from exchange.imtf.dmz [192.168.255.30]
	by imtfinter.imtf.ch
	with XWall v3.31 ;
	Thu, 6 Jan 2005 13:00:36 +0100
Received: by imtfexchange.imtf.ch with Internet Mail Service (5.5.2653.19)
	id <CK68STPP>; Thu, 6 Jan 2005 12:58:18 +0100
Message-ID: <DF7EC83D7AFBD411965B0008C7596EC5019902F6@imtfexchange.imtf.ch>
From: Maczka Michal <michal.maczka@imtf.ch>
To: 'Maven 2 Developers List' <m2-dev@maven.apache.org>
Subject: RE: #1 thoughts on the goal chain
Date: Thu, 6 Jan 2005 12:58:17 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N



> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: Thursday, January 06, 2005 12:13 PM
> To: 'Maven 2 Developers List'
> Subject: RE: #1 thoughts on the goal chain
> 
> 
> 
> 
> > -----Original Message-----
> > From: Maczka Michal [mailto:michal.maczka@imtf.ch]
> > Sent: jeudi 6 janvier 2005 12:02
> > To: 'Maven 2 Developers List'
> > Subject: RE: #1 thoughts on the goal chain
> 
> [snip]
> 
> > Simply goal aliasing like
> > 
> > test - > surefire:test
> > compile - > java:compile
> > 
> > which can be overridden per project basis is imo sufficient.
> 
> This is exactly what I have done in the caller plugin. Have 
> you seen it?
> 

Yes I saw caller plugin.
But this is not exactly the same thing but the idea is indeed quite close.

The idea here is that you have goals which belong to no plugin and m2 core
will be a mediator which will delegate this call to appropiate mojo
so plugins won't be requited to use other plugins.

For example jar:jar goal can have a dependecy on "compile" goal and m2 core
takes care to execute a goal which is bound to that name
(e.g. by default java:compile)

By the convetion in m2 all goals have two parts (e.g. java:compile) first
one which identifies the plugin which provide an implemention of that goal
(which is "java: in our case) , second which
identifies the mojo ("compile").  
Those orphan goals about which I was speaking above by convetion can have
just a single string in their names so they can be easly identified.




> The only issue is that it's a bit of a hack the way it's done 
> now (but it
> was the only solution I could think of for Maven 1). 

Most likly we are speaking about the same thing just impl. details are
different.

>Now, 
> we're discussing
> Maven 2 here and I think it's much cleaner to build it into the plugin
> descriptor.
> 



Michal