;)
-- gd
Maczka Michal wrote:
-Original Message-
From: Gilles Dodinet [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 10:26 PM
To: Maven Developers List
Subject: Re: cvs commit: maven-components USE-CASES.txt
hi-
here are a few comments on why ive added that thingy.
first
> -Original Message-
> From: Gilles Dodinet [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 18, 2004 10:26 PM
> To: Maven Developers List
> Subject: Re: cvs commit: maven-components USE-CASES.txt
>
>
> hi-
>
> here are a few comments on why ive added
hi-
here are a few comments on why ive added that thingy.
first let me say i dont actually think it would be a nice solution (as i
pointed it in the patch). i also agree that entities stuff are
error-prone especially in a multiproject context (i have indeed
experimented inconsistent behaviou
On Thu, 2004-03-18 at 06:18, Rafal Krzewski wrote:
> Maczka Michal wrote:
>
> >So what I am saying is that we should be only merging POMs not arbitrary XML
> >
> >
> Very good point. I personaly hate SGML entities mockery with all my
> heart - it's so ugly and so fragile! As for explicit inclus
On Thu, 2004-03-18 at 04:44, Maczka Michal wrote:
> Hi Jason!
>
> I think that for that particular use case which is described here it
> would be just simpler handle via what you are calling "group dependenies".
Possibly :-) I didn't really look that closely I just figured I might as
well get Gi
Maczka Michal wrote:
So what I am saying is that we should be only merging POMs not arbitrary XML
Very good point. I personaly hate SGML entities mockery with all my
heart - it's so ugly and so fragile! As for explicit inclusion of XML
bits, problems arise when they are used acorss multiple p
Hi Jason!
I think that for that particular use case which is described here it
would be just simpler handle via what you are calling "group dependenies".
It means that we can have a special dependency type (e.g.
group) rather then use complex XML structures/aliases.
This dependenecy type means: r
