Mailing-List: contact general-help@gump.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Gump code and data" <general@gump.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of brett.porter@gmail.com
 designates 66.249.82.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=XXTWmfB7ZxiFUcyJy7L49k/fY54Itj1IRPeQy10NsHG65GiEQtBSzofYgUqjYxRd7jrjo1g88PIyztDke+VWL6Zwktrmv66NEVdMuhTLztghVhKU64mRQoE/hzUdSwtGP97zfGrkxoyAnOcEl/QqTNGJHbwGrCoRsLZ5lF4RlOQ=
Message-ID: <9e3862d80511180305j1d781c6bpa9d052fc2b958893@mail.gmail.com>
Date: Fri, 18 Nov 2005 22:05:28 +1100
From: Brett Porter <brett.porter@gmail.com>
To: Gump code and data <general@gump.apache.org>
Subject: Re: Maven 2
In-Reply-To: <87br0j7tbo.fsf@www.samaflost.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <20051104065157.77032.qmail@minotaur.apache.org>
	 <dl85me$ktg$1@sea.gmane.org> <87veyvj0a3.fsf_-_@www.samaflost.de>
	 <20051114090031.GC77532@bali.sjc.webweaving.org>
	 <9e3862d80511140253x6ed2b123vacecba546cbfaae0@mail.gmail.com>
	 <87lkzqmqdf.fsf@www.samaflost.de>
	 <20051115201026.GD7782@bali.sjc.webweaving.org>
	 <87psp1kx12.fsf_-_@www.samaflost.de>
	 <9e3862d80511152145k5d3b8c69ja3073bbca877fe05@mail.gmail.com>
	 <87br0j7tbo.fsf@www.samaflost.de>

On 11/17/05, Stefan Bodewig <bodewig@apache.org> wrote:
> One thing that bothers me with Maven 1 from a Gump point of view is
> that I don't have any way to override jars that come bundled with
> Maven unless projects declare a dependency on them.

That's the same in m2, but its what you want as things are truly
separated (maven's are maven's, each plugins are their owns, the
project gets exactly what it declares). In m1 everything was shoved in
together.

>
> A few projects run tests without declaring a dependency on junit at
> all, and even if they did, I'm not sure where our jar would be used -
> just to compile the tests or also when the test plugin executes them?
>

Tests are run in an isolated classloader, so you have to declare a
junit dependency on the project.

> From what I read above this is going to become worse with an installed
> version of Maven 2.  So yes, any plan that allows us to really use the
> HEAD/trunk versions of Maven and all stuff Maven uses is very much
> appreciated.

This should be possible now.

- Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org