You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by "Adam R. B. Jack" <aj...@trysybase.com> on 2004/07/22 04:33:13 UTC
Fw: [CRIMSON] Crimson on JDK1.5
This seems (to me) the obvious outcome (although I had to ask).
Can anybody help me with why XERCES depends upon CRIMSON?
http://brutus.apache.org/gump/jdk15/xml-crimson/xml-crimson/details.html
http://brutus.apache.org/gump/jdk15/xml-crimson/xml-xerces/details.html
Is this an historical dependency? [Would that I had the resources to answer
my own questions, but then, I'd still rather get human insights to enhance
empirical.]
regards,
Adam
----- Original Message -----
From: "Elliotte Rusty Harold" <el...@metalab.unc.edu>
To: <ge...@xml.apache.org>
Cc: <ge...@xml.apache.org>
Sent: Wednesday, July 21, 2004 5:30 PM
Subject: Re: [CRIMSON] Crimson on JDK1.5
> At 5:00 PM -0600 7/21/04, Adam R. B. Jack wrote:
> >The Gump team are attempting a Gump on JDK 1.5, and getting stuck with
> >Crimson not compiling. Could somebody explain the future of crimson as it
> >relates to JDK1.5?
> >
> >
http://brutus.apache.org/gump/jdk15/xml-crimson/xml-crimson/index.html
> >
>
> There is no future. Crimson is dead. Java 1.5 will use Xerces.
> --
>
> Elliotte Rusty Harold
> elharo@metalab.unc.edu
> Effective XML (Addison-Wesley, 2003)
> http://www.cafeconleche.org/books/effectivexml
>
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fw: [CRIMSON] Crimson on JDK1.5
Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> > Is this an historical dependency? [Would that I had the resources to
answer
> > my own questions, but then, I'd still rather get human insights to
enhance
> > empirical.]
>
> Because I am evil? ;-)
Yup, you clearly have a perverse enjoyment of purist nuances. ;-)
> Ant requires an XML parser. Xerces 2 contained common code (or at least
> package names) with Xerces 1. The Xerces team routinely used Xerces 1
> in their build environment in order to build Xerces 2.
>
> Every once in a while, and completely unbeknownst to the Xerces
> development team, Xerces 2 would become broken or incomplete, but they
> would not know it because some aspect of Xerces 1 would "bleed through"
> the build environment.
>
> Compiling with a non-Xerces compiler allowed such problems to be
identified.
Hmm, interesting, I see. So, since xerces 1 and crimson are 'hibernated',
and since both JDK 1.4 and 1.5 (the main two JDK levels we Gump upon) both
come with an XML parser, ought we simply remove the dependency and force
Gump metadata to be 1.4|1.5 bound? Hmm, I'd half hoped to set up a JDK 1.3
Gump on Brutus, so we can help folks with both (likely) ends of the scale.
Is it time to teach Gump metadata about JDK level, somehow?
Thoughts?
regards,
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fw: [CRIMSON] Crimson on JDK1.5
Posted by Sam Ruby <ru...@apache.org>.
Adam R. B. Jack wrote:
> This seems (to me) the obvious outcome (although I had to ask).
>
> Can anybody help me with why XERCES depends upon CRIMSON?
>
> http://brutus.apache.org/gump/jdk15/xml-crimson/xml-crimson/details.html
> http://brutus.apache.org/gump/jdk15/xml-crimson/xml-xerces/details.html
>
> Is this an historical dependency? [Would that I had the resources to answer
> my own questions, but then, I'd still rather get human insights to enhance
> empirical.]
Because I am evil? ;-)
Ant requires an XML parser. Xerces 2 contained common code (or at least
package names) with Xerces 1. The Xerces team routinely used Xerces 1
in their build environment in order to build Xerces 2.
Every once in a while, and completely unbeknownst to the Xerces
development team, Xerces 2 would become broken or incomplete, but they
would not know it because some aspect of Xerces 1 would "bleed through"
the build environment.
Compiling with a non-Xerces compiler allowed such problems to be identified.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org