You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xml.apache.org by Edwin Goei <ed...@sun.com> on 2002/02/05 21:00:41 UTC
Re: [3rd party jar] crimson-ant, crimson-parser, jaxp
Vincent Hardy wrote:
>
> Hello,
>
> Following Dirk's email on third-party jars we have addressed the license
> issues in Batik on third-party jars (which was the point of the email),
> not on jars coming from Apache code. Note that this only required moving
> and renaming the license that we already included for the only real
> 3rd party jar we have.
>
> This is why we have not added license/readme for crimson, ant and jaxp
> which come from Apache and we did not consider as 3rd party (we think
> of the various Apache projects as being part of the same family, not
> third party).
>
> About jaxp, the commiter who added it to the Batik repository pointed
> that the source code was available under the Apache license in
> xml-commons
> so an additional license seemed superfluous:
>
> http://cvs.apache.org/viewcvs.cgi/xml-commons/java/external/src/javax/xml/parsers/
>
> may be Edwin could tell us if we got the wrong impression.
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.
-Edwin
---------------------------------------------------------------------
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
Re: [3rd party jar] crimson-ant, crimson-parser, jaxp
Posted by Edwin Goei <ed...@sun.com>.
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 !
Yup.
-Edwin
---------------------------------------------------------------------
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
Re: [3rd party jar] crimson-ant, crimson-parser, jaxp
Posted by Edwin Goei <ed...@sun.com>.
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 !
Yup.
-Edwin
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-dev-help@xml.apache.org
Re: [3rd party jar] crimson-ant, crimson-parser, jaxp
Posted by Dirk-Willem van Gulik <di...@covalent.net>.
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
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-dev-help@xml.apache.org
Re: [3rd party jar] crimson-ant, crimson-parser, jaxp
Posted by Dirk-Willem van Gulik <di...@covalent.net>.
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