[
https://issues.apache.org/jira/browse/APEXCORE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244021#comment-15244021
]
ASF GitHub Bot commented on APEXCORE-422:
-----------------------------------------
Github user tweise commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/309#issuecomment-210739152
I would defer release of a new artifact until late next week so we can drop
the -incubating at the same time. We also need more stability for checkstyle.
We just released the artifact and it is already obsolete?
Why is there an exception in PhysicalPlan? If it is a valid use of
annotation, then why do we not allow it elsewhere?
> Checkstyle rule related to allowSamelineParameterizedAnnotation should be
> just suppressed for DTCli and PhysicalPlan
> --------------------------------------------------------------------------------------------------------------------
>
> Key: APEXCORE-422
> URL: https://issues.apache.org/jira/browse/APEXCORE-422
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Fix For: 3.4.0
>
>
> The ticket was open to address the following issue which was reverted:
> Right now we are not letting users to write the following
> {code}
> for (@SuppressWarnings("deprecation")
> com.datatorrent.api.StatsListener.OperatorCommand cmd : rsp
> .operatorCommands)
> {code}
> We should suppress this rule only for DtCli and Physical Plan
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
