JSON licensing

Georg Kallidis

2018-10-22 13:36:20 UTC

Hi Jeffery,

thanks for this hint, again. Although I checked this already - Turbine
itself has optionally org.jabsorb, which is Apache 2 licensed and has
org.json packaged inside.

Fulcrum Json Jackson has an optional dependency via
Jackson-datatype-json-org as well, which was fixed to version 2.6.6
(before java 8). I updated it now to 2.8.11, as yes! the newest version
2.9.6 has removed org.apache.geronimo.bundles:json:jar:20090211_1 apache 2
compliant dependency with org.json 201718 dependency again!

Best regards, Georg

Von: Jeffery Painter <***@jivecast.com>
An: Turbine Developers List <***@turbine.apache.org>
Datum: 04.10.2018 13:20
Betreff: JSON licensing

Hi Georg,

I just read this... do you think the fulcrum/json package is impacted by
this? Might be good to check.

Thanks,
Jeff

-------- Forwarded Message --------
Subject: Re: Cloud clustering support using Kubernetes
Date: Thu, 4 Oct 2018 11:57:57 +0100

Hi,
I cannot find the original mail now (I think it was sent by Bertrand
Delacretaz two years ago) but json.org's licence is not ASL2 compatible.
For that reason several Apache projects (Apache Wicket one of them) had to
migrate to something else.
Wicket choose https://github.com/tdunning/open-json and then improved it to
https://github.com/openjson/openjson. The APIs are almost identical to make
the transition easier.

http://www.apache.org/legal/resolved.html#json

Mark

On Wed, Oct 3, 2018 at 10:27 PM Christopher Schultz <

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Rémy,

Hi,
As I talked about during the latest TomcatCon (and the previous one
in London actually ...), there's a cloud aware cluster members
provider that can be contributed to Tomcat.
https://github.com/rmaucher/tomcat-in-the-cloud It uses Kubernetes
to retrieve the members of a cluster, rather than multicast (which
isn't available) or static (which is well ... static) member
providers.
Credits: Maxime Beck and JGroups did the initial code Keiichi
Fujino explained how to refactor it to fit in the Catalina cluster
API and I refactored it as he told me to
Problems: Only does Kubernetes for now (which is likely ok since
it's now widely available) JSON parser dependency (org.json) that
package renaming using a script or include json code in Tomcat)

Solr uses this JSON parser which is quite fast, although the API is a
https://github.com/yonik/noggit
AL2 license
I'm not sure it's necessary to have a "streaming JSON" parser as
opposed to a more "traditional" one where the whole JSON object is
converted into objects before the client code can do anything with them.

The json from Kube is simple.
The org.json parser is very dom like, this event based one looks good I
guess. Is it worth changing my code ? Given the parser size, event based
nature and the presence of a "writer", this noggit could be worth package
renaming (IMO for this one that's the only viable strategy as I'm not sure
there's much maintenance or use going on - maybe it's bug free ;) ). After
all, we might need/use more json handling in Tomcat in the future (right
?).
Rémy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@tomcat.apache.org
For additional commands, e-mail: dev-***@tomcat.apache.org

[Anhang "signature.asc" gelöscht von Georg Kallidis/CeDiS/FU-Berlin/DE]