On Mon, 2004-04-19 at 09:00, Niclas Hedhman wrote:
> On Monday 19 April 2004 20:40, Jason van Zyl wrote:
> > Huh? You don't want to share dependencies anywhere?
>
> No. Just to say that
> xerces -> 2.4.0
> avalon-logkit -> 1.2
> jakarta-bcel -> 5.2
> log4j -> 1.2.1
>
> and so on.
>
> > > I wan
On Monday 19 April 2004 20:40, Jason van Zyl wrote:
> Huh? You don't want to share dependencies anywhere?
No. Just to say that
xerces -> 2.4.0
avalon-logkit -> 1.2
jakarta-bcel -> 5.2
log4j -> 1.2.1
and so on.
> > I want to have ONE place, where I can list the versions to use
> > for each arti
On Mon, 2004-04-19 at 07:57, Niclas Hedhman wrote:
> On Monday 19 April 2004 02:05, Jason van Zyl wrote:
>
> > To help you could give me a little tree description of your build and
> > describe how you would like things shared.
>
> > I would assume that ideally, you would like to a parent POM in
On Monday 19 April 2004 20:07, Vincent Massol wrote:
> This defeats the goal of centralizing dependency definitions. We find it
> better to have:
>
> &xml-apis;
This is really good tip... :o)
Niclas
--
+-//---+
| http://www.bali.ac |
| http://niclas.hedhman.or
Niclas Hedhman wrote on Monday, April 19, 2004 2:01 PM:
> On Monday 19 April 2004 04:11, Jörg Schaible wrote:
>
>> So my /myproject/build/entities directory contains the project.ent
>> and all the files that define the real entities like characters.ent,
>> versions.ent, ...
>>
>> project.ent co
> -Original Message-
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
> Sent: 19 April 2004 13:50
> To: Maven Developers List
> Subject: Re: XML Catalogs
>
>
> Ok. We understand this pattern, and IMHO it is not applicable at all,
> since
> you can't h
On Monday 19 April 2004 04:11, Jörg Schaible wrote:
> So my /myproject/build/entities directory contains the project.ent and all
> the files that define the real entities like characters.ent,
> versions.ent, ...
>
> project.ent contains the lines:
>
> %character-entities;
> %version-entities;
>
On Monday 19 April 2004 02:05, Jason van Zyl wrote:
> To help you could give me a little tree description of your build and
> describe how you would like things shared.
> I would assume that ideally, you would like to a parent POM in very
> top-level directory in order to share as much as possibl
soon
as a new artifact is inserted into the system (either external or internal).
I guess I have no other choice (since there is no interest in Maven for
catalogs) to change my plugin so that it either search/replace the mammoth
large file or recreates all the index.ent with the content in the ce
Niclas Hedhman wrote:
> On Sunday 18 April 2004 23:39, Jason van Zyl wrote:
>
>> You pretty gave no explanation as to why catalogs would be a good thing
>> other than saying:
>
> We are trying (@Avalon) the hardest to centralize the versioning of our
> 70+ versi
On Sun, 2004-04-18 at 13:35, Niclas Hedhman wrote:
> On Monday 19 April 2004 01:27, Jason van Zyl wrote:
> > so if the geronimo build is made to work then I
> > think Avalon will have a working model from which to copy.
>
> Ok... that, I guess, is something in the near future.
To help you could
bob mcwhirter wrote:
Ah, catalogs are actually a wonderful thing. They translate identifiers
to something system-specific, typically. They are mircales in SGML and
XML has been knocked for not having them previously.
Has the w3c done a catalog spec?
OASIS:
http://www.oasis-open.org/committees
On Sun, 2004-04-18 at 13:35, Niclas Hedhman wrote:
> On Monday 19 April 2004 01:27, Jason van Zyl wrote:
>
> > > We are trying (@Avalon) the hardest to centralize the versioning of our
> > > 70+ versioned artifacts, their cross-dependencies and all the external
> > > dependencies that are involved
nal Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 18 April 2004 19:27
> To: Maven Developers List
> Subject: Re: XML Catalogs
>
> On Sun, 2004-04-18 at 12:23, Niclas Hedhman wrote:
> > On Sunday 18 April 2004 23:39, Jason van Zyl wrote:
> >
> &g
On Sun, 18 Apr 2004, Jason van Zyl wrote:
> On Sun, 2004-04-18 at 13:19, bob mcwhirter wrote:
> > Ah, catalogs are actually a wonderful thing.
>
> Maybe so, but I still don't think we need them and if the xpp3 parser
> doesn't support them then we can't use
On Monday 19 April 2004 01:27, Jason van Zyl wrote:
> > We are trying (@Avalon) the hardest to centralize the versioning of our
> > 70+ versioned artifacts, their cross-dependencies and all the external
> > dependencies that are involved.
>
> I believe the fellow who manages development said he ha
On Sun, 2004-04-18 at 13:19, bob mcwhirter wrote:
> Ah, catalogs are actually a wonderful thing.
Maybe so, but I still don't think we need them and if the xpp3 parser
doesn't support them then we can't use them because I'm not using xerces
just to get catalog support. I
On Sun, 2004-04-18 at 12:23, Niclas Hedhman wrote:
> On Sunday 18 April 2004 23:39, Jason van Zyl wrote:
>
> > You pretty gave no explanation as to why catalogs would be a good thing
> > other than saying:
>
> We are trying (@Avalon) the hardest to centralize
On Monday 19 April 2004 01:19, bob mcwhirter wrote:
> Has the w3c done a catalog spec?
Not sure, but I think they either have, or are in the process of doing it...
Niclas
--
+-//---+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+--//-
Ah, catalogs are actually a wonderful thing. They translate identifiers
to something system-specific, typically. They are mircales in SGML and
XML has been knocked for not having them previously.
Has the w3c done a catalog spec?
-bob
On Sun, 18 Apr 2004, Jason van Zyl wrote:
>
On Sunday 18 April 2004 23:39, Jason van Zyl wrote:
> You pretty gave no explanation as to why catalogs would be a good thing
> other than saying:
We are trying (@Avalon) the hardest to centralize the versioning of our 70+
versioned artifacts, their cross-dependencies and all the ex
e interested, which probably
means we're not to keen on the idea, which most likely means your patch
won't get integrated.
You pretty gave no explanation as to why catalogs would be a good thing
other than saying:
---
I think it could solve a lot of
http://w
Hi,
Since noone reacted on my quest for XML Catalog support in Maven, I am
patching Maven myself to handle it.
I have 2 questions;
1. I'll submit a patch back to the community, so which branch should I make
the diff against.
2. In MavenUtils.getNonJellyProject(), there is a 1), 2) & 3) steps
Hi,
Does Maven contain Catalog support?
http://xml.apache.org/commons/components/resolver/resolver-article.html
I think it could solve a lot of
http://wiki.codehaus.org/maven/EnsureProjectConsistencyWithEntities
And if it would only be a matter of
import org.apache.xml.resolver.tools.CatalogRe
24 matches
Mail list logo
