On Mon, 14 Nov 2005, Brett Porter <[EMAIL PROTECTED]> wrote:
> We actually started validating the project.xml files. Some people
> have a lot of random content in there that was previously silenty
> ignored.
>
> Maybe its worth considering them a failed build for the purposes of
> Gump so that th
On Tue, Nov 15, 2005 at 06:28:28AM +0100, Stefan Bodewig wrote:
> On Mon, 14 Nov 2005, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> > We actually started validating the project.xml files. Some people
> > have a lot of random content in there that was previously silenty
> > ignored.
> >
> > Maybe i
On 11/16/05, Leo Simons <[EMAIL PROTECTED]> wrote:
[snip]
> Actually, someone's looking at changing the excalibur build to use maven
> 2. That pretty much means tree detoriation anyway. We're going to start
> seeing that all over apache as projects migrate to maven 2.
>
> cheers,
>
> LSD
Just out
On 11/16/05, Leo Simons <[EMAIL PROTECTED]> wrote:
> Actually, someone's looking at changing the excalibur build to use maven
> 2. That pretty much means tree detoriation anyway. We're going to start
> seeing that all over apache as projects migrate to maven 2.
In theory, Gump should be able to bu
I don't know of them all, but I believe the following projects are on
the way or considering it:
Cocoon, Pluto, JetSpeed 2, Struts, Excalibur, Geronimo, Directory, Felix
Those are the ones feeling pain points in their build that Maven
solves. For the ones where it already just works, there is pro
Brett Porter wrote:
I don't know of them all, but I believe the following projects are on
the way or considering it:
Cocoon, Pluto, JetSpeed 2, Struts, Excalibur, Geronimo, Directory, Felix
Add MyFaces (they are considering it) to the list (tobago is already maven2). Struts has an attempt
s
On Tue, 15 Nov 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
> Actually, someone's looking at changing the excalibur build to use
> maven 2. That pretty much means tree detoriation anyway. We're going
> to start seeing that all over apache as projects migrate to maven 2.
Pluto's trunk has already j
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
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
-->
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
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
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 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
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/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
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 Sun, 13 Nov 2005, Bill Barker <[EMAIL PROTECTED]> wrote:
> "Stefan Bodewig" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>> The version of dom4j that Maven 1.0.2 uses is quite old - some
>> prerelase of 1.4. Maybe we could upgrade to
ven 1.0.2 uses is quite old - some
> >> prerelase of 1.4. Maybe we could upgrade to Maven 1.1?
> >
> > I just tried with Maven 1.1b2, and Maven chokes on the Excalibur
> > project.xml long before getting to Struts. It looks like there
> > isn't enough backw
t;[EMAIL PROTECTED]> wrote in message
> > > news:[EMAIL PROTECTED]
> >
> > >> The version of dom4j that Maven 1.0.2 uses is quite old - some
> > >> prerelase of 1.4. Maybe we could upgrade to Maven 1.1?
> > >
> > > I just tried with Maven 1.
On Mon, Nov 14, 2005 at 09:53:01PM +1100, Brett Porter wrote:
> We probably need a compatibility option, but it's listed on the known
> incompatibility pages.
Aw, that sucks as a concept! I thought maven1 was going to stay compatible
and there'd be painfulness only once (maven1 -> maven2)?
> We a
On 11/14/05, Leo Simons <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 14, 2005 at 09:53:01PM +1100, Brett Porter wrote:
> > We probably need a compatibility option, but it's listed on the known
> > incompatibility pages.
>
> Aw, that sucks as a concept! I thought maven1 was going to stay compatible
> an
21 matches
Mail list logo
