apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vlad Rozov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-694) Use correct annotation for nullable and not nullable arguments
Date Tue, 25 Jul 2017 16:45:00 GMT

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

Vlad Rozov commented on APEXCORE-694:
-------------------------------------

No, it is not. IntelliJ and other IDE/static analysis tools do support jsr305 and can leverage
javax.annotation to find bugs. Usage of javax.validation.constraints does not have any impact
and does not result in any validation unless used to validate java beans. 

> Use correct annotation for nullable and not nullable arguments
> --------------------------------------------------------------
>
>                 Key: APEXCORE-694
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-694
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Vlad Rozov
>            Priority: Minor
>
> jsr305 suggests usage of javax.annotation.Nonnull. Usage of javax.validation.constraints.NotNull
should be avoided.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message