[jira] [Commented] (NIFI-391) Need ability to deprecate components

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user trixpan opened a pull request:

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

    NIFI-391 - Introduce the ability to deprecate a component

    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:
    - [X] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [X] 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.
    
    - [X] 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:
    - [X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [X] Have you written or updated unit tests to verify your changes?
    - [X] ~~~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)?~~~ 
    - [X] ~~~If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?~~~
    - [X] ~~~If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?~~~
    - [X] ~~~If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?~~~
    
    ### For documentation related changes:
    - [X] 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/trixpan/nifi NIFI-391

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

    https://github.com/apache/nifi/pull/1718.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 #1718
    
----
commit f4caef7b396701cda601749bb0e54cf5f5ba84d3
Author: Andre F de Miranda <tr...@users.noreply.github.com>
Date:   2017-04-29T03:09:22Z

    NIFI-3761 - adjust testFullyDocumentedProcessor to correctly eval to false when needed

commit eca1e2a465bedab060f26b2804e7e6d8c55b7e22
Author: Andre F de Miranda <tr...@users.noreply.github.com>
Date:   2017-04-29T06:06:15Z

    NIFI-391 - Introduce the ability to deprecate a component
    
    NIFI-439 - Allow documentation to inform user about deprecation
               of a component

----


> Need ability to deprecate components
> ------------------------------------
>
>                 Key: NIFI-391
>                 URL: https://issues.apache.org/jira/browse/NIFI-391
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework, Core UI, Extensions
>            Reporter: Mark Payne
>            Assignee: Andre F de Miranda
>
> The API should allow processors to be marked as deprecated such that the UI then shows on the graph that the Processor is deprecated.
> Additionally, the UI should show in the Status Bar that there are deprecated components (processors, reporting tasks, controller services) in the flow.
> This valuable because of improvements such as NIFI-377. In this case, we have a community member making the Base64EncodeContent processor more generic so that it can encode/decode base 16,32, and 64. At this point, Base64EncodeContent doesn't make sense as a name, so there is a more generic EncodeContent processor. We don't need both, so we want to deprecated the Base64EncodeContent processor.



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