[ 
https://issues.apache.org/jira/browse/NIFI-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668398#comment-15668398
 ] 

ASF GitHub Bot commented on NIFI-2991:
--------------------------------------

GitHub user joewitt opened a pull request:

    https://github.com/apache/nifi/pull/1230

    NIFI-2991 takes care of all known 1.x issues for json.org dependency

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/joewitt/incubator-nifi NIFI-2991

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1230.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1230
    
----
commit 34413b987dd92c4d892966524023f239a37c7abb
Author: joewitt <[email protected]>
Date:   2016-11-15T20:48:36Z

    NIFI-2991 removed usage of json lib and components still using it

commit 748ce79a7d64a73c20d2fd5dc863e524700fe434
Author: joewitt <[email protected]>
Date:   2016-11-15T20:52:17Z

    Revert "NIFI-1893 Add processor for validating JSON"
    
    This reverts commit f11682202b57edab585967e033839800d4159f4e.

commit 1c60368b1bb8ba9129d32f176174d2f2682b9071
Author: joewitt <[email protected]>
Date:   2016-11-15T21:17:48Z

    NIFI-2991 removed json.org references as appropriate for build.  Twitter 
proc no longer deployed but reference kept in notice just in case someone uses 
it

----


> JSON.org license is now CatX
> ----------------------------
>
>                 Key: NIFI-2991
>                 URL: https://issues.apache.org/jira/browse/NIFI-2991
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Sean Busbey
>            Assignee: Joseph Witt
>            Priority: Blocker
>             Fix For: 1.1.0
>
>
> per [update resolved legal|http://www.apache.org/legal/resolved.html#json]:
> {quote}
> CAN APACHE PRODUCTS INCLUDE WORKS LICENSED UNDER THE JSON LICENSE?
> No. As of 2016-11-03 this has been moved to the 'Category X' license list. 
> Prior to this, use of the JSON Java library was allowed. See Debian's page 
> for a list of alternatives.
> {quote}
> I don't know how many of our versions include stuff under this license, it's 
> definitely currently in master.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to