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

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

GitHub user dlukyanov opened a pull request:

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

    NIFI-3688 Extended Groovy Nifi Processor 

    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:
    - [YES] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
     in last one only
    
    - [YES] 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.
    
    - [YES] Has your PR been rebased against the latest commit within the 
target branch (typically master)?
    
    - [YES?] Is your initial contribution a single, squashed commit?
     
    ### For code changes:
    - [YES] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
    - [NO] Have you written or updated unit tests to verify your changes?
     no changes done to existing code. but no tests to groovyx processor.
    - [YES] 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)? 
    - [YES?] If applicable, have you updated the LICENSE file, including the 
main LICENSE file under nifi-assembly?
    - [YES?] If applicable, have you updated the NOTICE file, including the 
main NOTICE file found under nifi-assembly?
    - [NO] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?
     not applicable?
    ### For documentation related changes:
    - [YES] 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/dlukyanov/nifi master

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

    https://github.com/apache/nifi/pull/1662.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 #1662
    
----
commit 279e0502deef66d2a2934a211430aac52d3a5b28
Author: dlukyanov <[email protected]>
Date:   2017-04-02T07:55:22Z

    groovyx initial version

commit 0bb6f9f970b186b6ec018d70e5afa68c9345b7c1
Author: dlukyanov <[email protected]>
Date:   2017-04-10T21:09:54Z

    https://issues.apache.org/jira/browse/NIFI-3688

commit 8d142dd629fee4f42434f754c16c897edfa08447
Author: dlukyanov <[email protected]>
Date:   2017-04-10T21:22:38Z

    NIFI-3688 license update to ASF

commit cd26cb1f3f2ebcbdc2ebda8904c424c62f2e5298
Author: dlukyanov <[email protected]>
Date:   2017-04-10T21:24:30Z

    NIFI-3688 add groovyx dependency

----


> Create extended groovy scripting processor
> ------------------------------------------
>
>                 Key: NIFI-3688
>                 URL: https://issues.apache.org/jira/browse/NIFI-3688
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Dmitry Lukyanov
>            Priority: Minor
>
> The idea is to simplify groovy scripting.
> Main targets:
> - to be compatible with existing groovy scripting
> - simplify read/write attributes
> - simplify read/write content
> - avoid closure casting to nifi types like `StreamCallback`
> - simplify and provide visibility when accessing to controller services from 
> script



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to