Re: [DISCUSS] JSON.org license is now category-x

Hello, I’ve just pushed an update to https://github.com/steveblackmon/incubator-streams/tree/STREAMS-496 Added extensive testing around oauth request signing, which is now working according to twitter. Now working on the juneau RestClient bindings to get the results populated into streams

Re: [DISCUSS] JSON.org license is now category-x

I created  https://cwiki.apache.org/confluence/display/STREAMS/Twitter+Provider+Refactor  with a more concrete proposal for how to do this.  I welcome feedback or any volunteers who want to help. Steve On March 6, 2017 at 10:59:44 AM, sblackmon (sblack...@apache.org) wrote:   So this is still

Re: [DISCUSS] JSON.org license is now category-x

  So this is still something we need to take care of, and the clock is ticking down to April 30 2017. I opened STREAMS-496 this morning. I think it will be straight-forward to remove the twitter4j client from the providers, at least from a request / response perspective, using our twitter

Re: [DISCUSS] JSON.org license is now category-x

On 2016-11-14 17:04 (-), Joey Frazee wrote: > The ASF recently reclassified the JSON license for org.json as category-x > because of its "shall be used for Good, not Evil" clause [1]. > > There does not appear to be any direct usage of it in Streams but there are

Re: [DISCUSS] JSON.org license is now category-x

The PR is a year old so I'm not sure whether we can count on it. Can see if we can push it along though. > On Nov 14, 2016, at 11:41 AM, sblackmon wrote: > > Looking into this it’s already on Twitter4J’s radar and there’s an open > pull-request. > >

Re: [DISCUSS] JSON.org license is now category-x

I don't think dependency:tree transitively follows all the way through, so we actually don't see the violators. > On Nov 14, 2016, at 12:00 PM, Suneel Marthi wrote: > > mvn dependency:tree (or something like that) > > it gives all libs along with their dependent libs

Re: [DISCUSS] JSON.org license is now category-x

mvn dependency:tree (or something like that) it gives all libs along with their dependent libs On Mon, Nov 14, 2016 at 6:41 PM, sblackmon wrote: > Thanks for bringing this up Joey. > > Looking into this it’s already on Twitter4J’s radar and there’s an open > pull-request.

Re: [DISCUSS] JSON.org license is now category-x

Thanks for bringing this up Joey. Looking into this it’s already on Twitter4J’s radar and there’s an open pull-request. https://github.com/yusuke/twitter4j/pull/215 Provided they resolve and release again in the near future, the only action we’ll need to take is to upgrade. Any ideas on ways

[DISCUSS] JSON.org license is now category-x

The ASF recently reclassified the JSON license for org.json as category-x because of its "shall be used for Good, not Evil" clause [1]. There does not appear to be any direct usage of it in Streams but there are a number of dependencies in Streams that do depend on org.json, most notably