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. If they are supported by the xpp3 parser
then I would make any changes necessary to make them available for
people to use if it was really deemed necessary. But I don't think they
will be and I'll try to show so with a large set of generated projects
which are highly nested to mimic something like Vincent's setup, the
Avalon setup, Plexus setup and the Geronimo setup.

> 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 Sun, 2004-04-18 at 10:37, Niclas Hedhman wrote:
> > > Hi,
> > >
> > > Since noone reacted on my quest for XML Catalog support in Maven, I am
> > > patching Maven myself to handle it.
> >
> > Probably not the most rational approach. If none of the developers
> > responded it more likely means none of us are 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://wiki.codehaus.org/maven/EnsureProjectConsistencyWithEntities
> >
> > ---
> >
> > > I have 2 questions;
> > >
> > > 1. I'll submit a patch back to the community, so which branch should I make
> > > the diff against.
> >
> > You should probably make an attempt to explain yourself a little more
> > clearly before potentially wasting your time.
> >
> > For one, I don't really even know what catalogs are or how they are
> > used, or how they would be of benefit maven. The other thing is that if
> > catalog support is something only supported by things like xerces and
> > not simple parsers like the xpp3 parser then it's definitely not going
> > to survive into maven2.
> >
> > Additionally the patch is certainly not going in before the 1.0 release.
> >
> > > 2. In MavenUtils.getNonJellyProject(), there is a 1), 2) & 3) steps. Would it
> > > be possible for the 2) step (MavenUtils.createContext() ) to be done first,
> > > and the 1) second??  Reason is, I want to pick up properties from the
> > > project.properties and pass it into the parser.
> > >
> > >
> > > Cheers
> > > Niclas
> >
> > --
> > jvz.
> >
> > Jason van Zyl
> > [EMAIL PROTECTED]
> > http://maven.apache.org
> >
> > happiness is like a butterfly: the more you chase it, the more it will
> > elude you, but if you turn your attention to other things, it will come
> > and sit softly on your shoulder ...
> >
> >  -- Thoreau
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> --
> Bob McWhirter        [EMAIL PROTECTED]
> The Werken Company   http://werken.com/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to