[
https://issues.apache.org/jira/browse/FLINK-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15476138#comment-15476138
]
ASF GitHub Bot commented on FLINK-4462:
---------------------------------------
Github user ramkrish86 commented on the issue:
https://github.com/apache/flink/pull/2412
@StephanEwen
As said above am not sure how to use the japicmp library. I can see that
from the IDE am not able to use any of the APIs provided from the library. May
be am missing something?
Also reading the docs of japicmp it says how to pass two different versions
of a jar file and see what are the public interface differences. So am not sure
how japicmp internally does it.
Do you have an problem in adding this RUN_TIME annotation? I think it
helps in adding plain java reflection based utils to idenfity
classes/interfaces missing them.
I can update my PR based on your thoughts on jaipcmp usage.
> 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)
