ts of the json.org code. This code is compatible, but lacks some
> >>> coverage. It also could lead to jar hell if used unjudiciously because
> it
> >>> uses the org.json package. Shading and exclusion in a pom might help.
> Or
> >>> not. Go with caution here.
> >
es move away from problem code. I have sent a
> pull
> > > >>>> request to twitter4 <https://github.com/yusuke/twitter4j/pull/254
> > >j,
> > > for
> > > >>>> example, that eliminates the problem. If they accept the pull,
> >>>> example, that eliminates the problem. If they accept the pull, then
> > all
> > >>>> would be good for the projects that use twitter4j (and thus
> json.org)
> > >>>>
> > >>>> 3) replace the json.org artifact with a compatible one th
;> I have created and published an artifact based on clean-room Android
> code
> >>>> <https://github.com/tdunning/open-json> that replicates the most
> >>>> important
> >>>> parts of the json.org code. This code is compatible, but lacks some
ished an artifact based on clean-room Android code
>>>> <https://github.com/tdunning/open-json> that replicates the most
>>>> important
>>>> parts of the json.org code. This code is compatible, but lacks some
>>>> coverage. It also could lead to
ates the most
>>> important
>>> parts of the json.org code. This code is compatible, but lacks some
>>> coverage. It also could lead to jar hell if used unjudiciously because it
>>> uses the org.json package. Shading and exclusion in a pom might help. Or
>>>
equires code
changes, but is probably a good thing to do. This option is the one that is
best in the long-term but is also the most expensive.
-- Forwarded message --
From: Jim Jagielski
Date: Wed, Nov 23, 2016 at 6:10 AM
Subject: JSON License and Apache Projects
To: ASF Board
(
d unjudiciously because it
> > uses the org.json package. Shading and exclusion in a pom might help. Or
> > not. Go with caution here.
> >
> > 4) switch to safer alternatives such as Jackson. This requires code
> > changes, but is probably a good thing t
gt; 4) switch to safer alternatives such as Jackson. This requires code
> changes, but is probably a good thing to do. This option is the one that is
> best in the long-term but is also the most expensive.
>
>
> -- Forwarded message --
> From: Jim Jagielski
> Da
tion is the one that is
best in the long-term but is also the most expensive.
-- Forwarded message --
From: Jim Jagielski
Date: Wed, Nov 23, 2016 at 6:10 AM
Subject: JSON License and Apache Projects
To: ASF Board
(forwarded from legal-discuss@)
As some of you may know, recent
10 matches
Mail list logo
