Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Wed, 24 Aug 2016 09:39:21 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12999531.1472023720000.395119.1472031561032@Atlassian.JIRA>
In-Reply-To: <JIRA.12999531.1472023720000@Atlassian.JIRA>
References: <JIRA.12999531.1472023720000@Atlassian.JIRA> <JIRA.12999531.1472023720991@arcas>
Subject: [jira] [Commented] (FLINK-4462) Add RUN_TIME retention policy for
 all the flink annotations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 24 Aug 2016 09:39:23 -0000


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

ASF GitHub Bot commented on FLINK-4462:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/2412
  
    Is that needed? The `japicmp` plugin can work with the annotations without runtime retention. Would be great if that plugin can check the presence of annotations, that seems like the right place.


> Add RUN_TIME retention policy for all the flink annotations
> -----------------------------------------------------------
>
>                 Key: FLINK-4462
>                 URL: https://issues.apache.org/jira/browse/FLINK-4462
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Minor
>
> It is better to add RUNTIME retention policy to flink annotations. So that utilites/tests can be added to ensure if the classes/interfaces are all tagged with proper annotations. 


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