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 (athena.apache.org: domain of kristian.rosenvold@gmail.com
 designates 209.85.218.215 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=Q5sE8A+WpOtW0nxeVU2hmEw/w6S9fF7ASJuurSksDKltgAjd0M48cWXLSuzWxXEbpH
         lyekvMH5oBQ1NoUGjAqYjZfCIMjnXBODbJ0AR3gnnujDAf6I9N7KBRyGt5TwvJdH/aBY
         oJYCkMvqsmAyQ5AnKewoiwbCBTL8XNWtSfQZ0=
MIME-Version: 1.0
In-Reply-To: <88c1b41002080158g7c6eb3b0lbceee7ed944ffd9c@mail.gmail.com>
References: <CDE1AF6C-19B5-4828-8631-CE0B017CBC59@visi.com>
	 <B5C61039-C7E8-42B4-9902-D694A69361E5@apache.org>
	 <2902EFED-09E7-464A-AFDE-7DD524413F69@visi.com>
	 <1257300563.2786.1.camel@office>
	 <0A0F9CC7-4756-4FAC-9FCF-EDBEC6490A40@apache.org>
	 <1265483784.11375.23.camel@office>
	 <0C52D4B3-0389-4114-A642-3DB0FC509C0C@apache.org>
	 <42a010a61002080118x382e3999hc22571212ef80947@mail.gmail.com>
	 <88c1b41002080158g7c6eb3b0lbceee7ed944ffd9c@mail.gmail.com>
Date: Mon, 8 Feb 2010 12:20:44 +0100
Message-ID: <42a010a61002080320k31c4b8f5pafaf4b88f1122c87@mail.gmail.com>
Subject: Re: Dependency on system property user.dir
From: Kristian Rosenvold <kristian.rosenvold@gmail.com>
To: Maven Developers List <dev@maven.apache.org>
Content-Type: multipart/alternative; boundary=000325559a92fe0945047f14fd29

--000325559a92fe0945047f14fd29
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Feb 8, 2010 at 10:58 AM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote

>
> >I think it would be acceptable to break a build if forkmode=never and
> >parallel build=true... i.e. have the maven api's expose the fact that we
> are
> >running in a parallel build, and then surefire can bomb the build out
> saying
> >that forkmode=never is incompatible with parallel builds... then the user
> >can decide to switch back to forkmode=once, or not use parallel builds...
>
> Good solution, I'll give that a try.


> I think that there are a number of other plugins which might want to be
> aware of a parallel build... e.g. maven-invoker-plugin, jetty-maven-plugin,
> etc... so I do think that the maven 3 API's need to have some mechanism of
> exposing to plugins that they are running in a parallel build.... how we
> add
> this information in such a way that plugins will still work for 2.x as well
> as 3.x is an interesting question
>
>
There will be some shared resources like tcp-ports that you probably can get
away with
just configuring per-module (and for jetty-maven-plugin I think this
works).

Anyone have any suggestions on how plugins should find out if
they're being run in parallel ?

Kristian

--000325559a92fe0945047f14fd29--