Brett's message from a while back which may be of interest to bill. There's
more in this thread...
LSD
- Forwarded message from Brett Porter <[EMAIL PROTECTED]> -
From: Brett Porter <[EMAIL PROTECTED]>
Date: Wed, 16 Nov 2005 16:45:56 +1100
Subject: Re: Maven 2
On 11/19/05, Leo Simons <[EMAIL PROTECTED]> wrote:
> Maven is in the center of the developers for a project (they type "mvn"
> and not "gump") so what these people want to author is a POM. Gump should
> read that POM and understand it.
Sorry, I probably didn't explain where I was coming from. Mave
On Fri, Nov 18, 2005 at 11:10:24PM +1100, Brett Porter wrote:
> > Why do you keep referring to a something.xml? Is it going to be a lot
> > easier to have the maven jar resolver read a something.xml rather than do
> > something else (like, I dunno, a database, or an XML/RPC interface, or
> > ...)?
On 11/18/05, Leo Simons <[EMAIL PROTECTED]> wrote:
> Bing! Light bulb went on in my head. Pull not push. I'm trying to think
> about an easy way to do the pull stuff, but that is probably all dependent
> on the mechanisms maven employs.
I'm pretty sure I can do this.
>
> Both gump and maven 2 are
I missed a bit..
On Fri, Nov 18, 2005 at 10:27:53PM +1100, Brett Porter wrote:
> On 11/16/05, Leo Simons <[EMAIL PROTECTED]> wrote:
> > I wrote an answer then deleted it. I got lost a little. Seperating concerns:
> >
> > --> support for maven2 in gump2
> > --> I'm not going to work on it
>
On Fri, Nov 18, 2005 at 10:27:53PM +1100, Brett Porter wrote:
> Yes, but you are going to have to go the other way around. It's a
> component that resolves artifacts and metadata. It doesn't get fed, it
> hunts.
Bing! Light bulb went on in my head. Pull not push. I'm trying to think
about an easy
On 11/16/05, Leo Simons <[EMAIL PROTECTED]> wrote:
> I wrote an answer then deleted it. I got lost a little. Seperating concerns:
>
> --> support for maven2 in gump2
> --> I'm not going to work on it
Fine by me. I assume gump3 is not far off then?
> --> how to properly support maven2 in
I'll be more specific.
If M2_HOME is set, then that is where the main libraries are located
from (its the install directory). You can run without it, eg
/some/random/install/bin/mvn and it will use /some/random/install as
the home directory.
For ~/.m2 - the default location of settings.xml is
~/.
On 11/17/05, Stefan Bodewig <[EMAIL PROTECTED]> 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 thi
Leo Simons wrote on Friday, November 18, 2005 9:49 AM:
> On Fri, Nov 18, 2005 at 12:20:39AM -0800, Bill Barker wrote:
[snip]
>> I believe that both the Maven1 and Maven2 scripts use $MAVEN_HOME,
>> which is the biggest problem with just creating a tag for
>> Gump2. There are also problems with s
On Fri, Nov 18, 2005 at 12:20:39AM -0800, Bill Barker wrote:
> "Stefan Bodewig" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > On Wed, 16 Nov 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
> >
> >> --> support for maven2 in gump2
> >> --> I'm not going to work on it
> >
> >
"Stefan Bodewig" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Wed, 16 Nov 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
>
>> --> support for maven2 in gump2
>> --> I'm not going to work on it
>
> I'd offer to do a monkey-see-monkey-do support if it is not too
> different
On Wed, 16 Nov 2005, Brett Porter <[EMAIL PROTECTED]> wrote:
> Because it has an even more online nature (plugins are not
> preinstalled), to use an installed version we'd again need to create
> a minimal local repository including those plugins, then use offline
> mode (-o), and ensure it can't g
On Wed, 16 Nov 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
> --> support for maven2 in gump2
> --> I'm not going to work on it
I'd offer to do a monkey-see-monkey-do support if it is not too
different from maven 1 support. In general I agree that gump3 is the
way to go and that we should
I wrote an answer then deleted it. I got lost a little. Seperating concerns:
--> support for maven2 in gump2
--> I'm not going to work on it
--> support for maven2 in gump3
--> pretty much like we did for maven1 + bootstrap
--> doing it quickly
--> not me
-->
Ok, here's the opportunity for me to write the mail in my head.
Aside from the non-existance of a gump machine right now, what is
needed to use Maven 2,
a) minimally
b) ideally
Because it has an even more online nature (plugins are not
preinstalled), to use an installed version we'd again need to
16 matches
Mail list logo
