> -Original Message-
> From: Maczka Michal [mailto:[EMAIL PROTECTED]
> Sent: 04 May 2004 12:03
> To: 'Maven Developers List'
> Subject: RE: [maven2] Anything Groovy in Maven2?
>
[snip]
> >
> > commons-logging is the best match I can think of
On Tue, 4 May 2004, Maczka Michal <[EMAIL PROTECTED]> wrote:
> ant2 development has never really started but is rather clear that
> it is a very different animal then ant1 and the code as a whole
> cannot be reused.
I'd rather say that there will never be an Ant2 in the way we tought
we would cre
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 04, 2004 8:53 AM
> To: 'Maven Developers List'
> Cc: 'Stefan Bodewig'
> Subject: RE: [maven2
[...]
> Agreed. It's almost there but a little push towards even better
> separation from Ant core is re
On Tue, 4 May 2004, Vincent Massol <[EMAIL PROTECTED]> wrote:
> I've talked to Stefan and he's very open to work with us,
he is 8-) And he's been subscribed to maven-dev for many months.
> - lifecycle IF (that can be solved easily by saying all tasks are
> thread safe)
This should be true for
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 04/05/2004 04:53:29 PM:
> Hmmm I think we need to talk more about this and involve the Ant
> team in the discussion as we need their help anyway. I'd prefer it to be
> in the Ant codebase (provided they are ok - If not I agree it could be
> done in
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> Sent: 04 May 2004 08:34
> To: Maven Developers List
> Subject: RE: [maven2] Anything Groovy in Maven2?
>
> "Vincent Massol" <[EMAIL PROTECTED]> wrote on 04/05/2004 04:14:03
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 04/05/2004 04:14:03 PM:
> Several things:
> - when you talk about "refactoring out", do you mean refactor out within
> the Ant project or copy-paste the code somewhere else?
Initially into the Maven code base. But later on, sharing with Ant would
be
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: 04 May 2004 07:55
> To: 'Maven Developers List'
> Subject: RE: [maven2] Anything Groovy in Maven2?
>
>
>
> > -Original Message-
> > From: [EMAIL PROTE
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> Sent: 04 May 2004 03:47
> To: [EMAIL PROTECTED]
> Subject: RE: [maven2] Anything Groovy in Maven2?
>
> Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 01:11:12 AM:
>
>
&
Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 02:29:27 PM:
[snip]
> Read what was written, it is the POJO. The Plugin, AbstractPlugin,
> PluginExecutionRequest and PluginExecutionResponse are the 3k of
> dependencies mentioned in the previous email. The PluginExecutionRequest
> still have
On Mon, 2004-05-03 at 22:55, [EMAIL PROTECTED] wrote:
> Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 12:17:13 PM:
>
> [snip good stuff]
>
> > No, if you actually looked at code you'll see it's not. There are tests
> > for the 4 varieties and even the fourth variety only requires a 3k dep
Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 01:11:12 AM:
> It's easy to solve, don't code things as Ant tasks. If you're doing
> something new then there is absolutely no reason to bind your code to
> Ant. Make POJO and wrap it.
Can we do the same for Maven2 then? i.e.
"It's easy to s
On Mon, 2004-05-03 at 21:46, [EMAIL PROTECTED] wrote:
> Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 01:11:12 AM:
>
>
> > It's easy to solve, don't code things as Ant tasks. If you're doing
> > something new then there is absolutely no reason to bind your code to
> > Ant. Make POJO and w
Jason van Zyl <[EMAIL PROTECTED]> wrote on 04/05/2004 12:17:13 PM:
[snip good stuff]
> No, if you actually looked at code you'll see it's not. There are tests
> for the 4 varieties and even the fourth variety only requires a 3k dep
> which does not really have anything to do with Maven2. They are
14 matches
Mail list logo
