Return-Path: 
 <dev-return-86887-apmail-maven-dev-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-dev-archive@www.apache.org
Received: (qmail 11258 invoked from network); 10 Nov 2008 01:00:54 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 10 Nov 2008 01:00:54 -0000
Received: (qmail 53580 invoked by uid 500); 10 Nov 2008 01:01:00 -0000
Delivered-To: apmail-maven-dev-archive@maven.apache.org
Received: (qmail 53502 invoked by uid 500); 10 Nov 2008 01:01:00 -0000
Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@maven.apache.org>
List-Help: <mailto:dev-help@maven.apache.org>
List-Post: <mailto:dev@maven.apache.org>
List-Id: "Maven Developers List" <dev.maven.apache.org>
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Delivered-To: mailing list dev@maven.apache.org
Received: (qmail 53491 invoked by uid 99); 10 Nov 2008 01:01:00 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Nov 2008 17:01:00 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of cs@schulte.it designates
 217.69.77.126 as permitted sender)
Received: from [217.69.77.126] (HELO smtp.rent-a-mailserver.de)
 (217.69.77.126)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Nov 2008 00:59:41 +0000
Received: from [192.168.10.198] (cable-82-119-21-16.cust.blue-cable.de
 [82.119.21.16])
	(user=cs@schulte.it mech=CRAM-MD5 bits=0)
	by smtp.rent-a-mailserver.de (8.13.8/8.13.8/Debian-3) with ESMTP id
 mAA10GSp015998
	for <dev@maven.apache.org>; Mon, 10 Nov 2008 02:00:16 +0100
Message-ID: <4917879E.7030709@schulte.it>
Date: Mon, 10 Nov 2008 02:00:14 +0100
From: Christian Schulte <cs@schulte.it>
User-Agent: Icedove 1.5.0.14eol (X11/20080724)
MIME-Version: 1.0
To: Maven Developers List <dev@maven.apache.org>
Subject: Re: Default plugin execution id
References: <4914A8FD.5030007@redhat.com>
	 <2BABBE7D2A66E04DB8A66A527D29927E4049F6@intrepid.infinity.nu>
	 <4914B080.4020003@redhat.com>
	 <2BABBE7D2A66E04DB8A66A527D29927E4049F7@intrepid.infinity.nu>
	 <491510F0.9090807@schulte.it>
	 <C85EA707-06A2-43EA-BE84-884AE777BAA7@apache.org>
	 <491568BF.6070304@udo.edu>
	 <22CBE890-5830-4D0B-A2AD-5063FF86CA14@sonatype.com>
	 <4916C8F1.3030604@udo.edu>
	 <2BABBE7D2A66E04DB8A66A527D29927E404A04@intrepid.infinity.nu>
 <88c1b40811091239p6b6587f5pb759425373a2bc2a@mail.gmail.com>
In-Reply-To: <88c1b40811091239p6b6587f5pb759425373a2bc2a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH,
 not delayed by milter-greylist-4.0.1 (smtp.rent-a-mailserver.de
 [217.69.77.126]); Mon, 10 Nov 2008 02:00:16 +0100 (CET)
X-Virus-Scanned: ClamAV version 0.94,
 clamav-milter version 0.94 on smtp.rent-a-mailserver.de
X-Virus-Status: Clean
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on
	smtp.rent-a-mailserver.de
X-Virus-Checked: Checked by ClamAV on apache.org
X-Old-Spam-Status: No, score=-0.7 required=8.0 tests=AWL,BAYES_00,RCVD_IN_PBL,
	RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=no version=3.2.3

Stephen Connolly wrote:
> AFAIK,
> 
> The execution id refers only to a specific plugin, and each execution can
> only match a specific phase... so I don't see the need to tie the execution
> to a goal name, neither to the plugin name...
> 
> What I see as bind important is if the plugin is bound to multiple phases
> and you want to configure the different phases differently...
> 
> At that point I think you're left with "breaking" the id as an id.... and
> you'd end up using a wild-card type matching, e.g.
> 
> <id>lifecycle:jar:*</id>
> 
> or
> 
> <id>lifecycle:*:compile</id>
> 
> or
> 
> <id>lifecycle:*:*</id>
> 
> All of which are useful, and do not require a schema change, and are rather
> unlikely to interfere with existing builds... but it feels ugly to me... and
> yet I'm proposing it! ;-)
> 

There must not necessarily be a lifecycle in use at all. How would this
execution id match standalone executions ? E.g.

mvn eclipse:eclipse
mvn netbeans-freeform:generate-netbeans-project

Consider a plugin with multiple such standalone goals for which a user
needs to provide configurations per goal. Neither the lifecycle nor the
packaging plays any role here, I think. E.g.

mvn ide:eclipse
mvn ide:netbeans-freeform

<id>none:*:none</id> ?

-- 
Christian


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