xmlgraphics-batik-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edwin Goei <edwi...@sun.com>
Subject Re: [3rd party jar] crimson-ant, crimson-parser, jaxp
Date Fri, 08 Feb 2002 01:39:26 GMT
Dirk-Willem van Gulik wrote:
> 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 :-)

Not sure what you are saying exactly in your last sentence, but I'd
interpret Sun's behavior to mean that management has lots of tasks to
work on and this particular license issue w/ jaxp.jar and Apache ends up
being very low priority.  In this case, we don't even need the old
jaxp.jar so the problem is solved.

> 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 !



To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-dev-help@xml.apache.org

View raw message