Mailing-List: contact general-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@xml.apache.org
Date: Thu, 7 Feb 2002 12:55:09 +0100 (CET)
From: Dirk-Willem van Gulik <dirkx@covalent.net>
To: general@xml.apache.org
cc: Vincent Hardy <vincent.hardy@sun.com>, <batik-dev@xml.apache.org>,
   <twleung@sauria.com>
Subject: Re: [3rd party jar] crimson-ant, crimson-parser, jaxp
In-Reply-To: <3C6039E9.67F91DF7@sun.com>
Message-ID: <Pine.OSX.4.43.0202071252060.494-100000@gandalf>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 5 Feb 2002, Edwin Goei wrote:

..
> There are different versions of Crimson.  Old versions used a jaxp.jar
> binary from Sun that shipped w/ the Sun Binary Code License.  Newer
> versions of Crimson use code from xml-commons that are under the ASF
> license.  So the fix is to use a newer version of Crimson.  If the
> reason you are using the old "jaxp.jar" is because of Ant, then you can
> upgrade to a newer version of Ant that uses a newer version of Crimson.
>
> BTW, I don't think anyone at Sun really cares that jaxp.jar is being
> distributed by Apache, but the PMC does which is the reason for this
> fire drill.

Ack.

Unfortunately - to the best of my knowledge we have however never gotten
the required license from Sun to allow distribution of the old jaxp.jar.
So it is fair to conclude their lawyers/IP guardians care enough :-)

Obviously - if required you can get assistance from the ASF should you
want us to go back to Sun and try agian to negotioate such.

But given that the new jaxp.jar is 100% ASF, supersedes the old one and
has all the features needed to replace the old one - it does not make much
sense. Thanks for solving this !

Dw


---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org