[
https://issues.apache.org/jira/browse/ACCUMULO-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-1863.
-----------------------------------------
Resolution: Won't Fix
This issue proposes only adding the dependency, to make the annotations
available for use later. However, we enforce dependency reduction, so we
wouldn't add the dependency unless we actually needed to use the annotations.
If use of these annotations is still desired, please open a new issue or pull
request at https://github.com/apache/accumulo
> Make JCIP annotations available
> -------------------------------
>
> Key: ACCUMULO-1863
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1863
> Project: Accumulo
> Issue Type: Improvement
> Reporter: Bill Havanki
> Priority: Trivial
> Labels: newbie
>
> During review of ACCUMULO-1556, it occurred to me that it could be beneficial
> to integrate the JCIP annotations (["old" JCIP
> site|http://jcip.net.s3-website-us-east-1.amazonaws.com/]). The annotations
> point out where code is thread-safe and not thread-safe, immutable objects,
> and items where access is guarded by a lock (object). By themselves the
> annotations do nothing, but static analysis tools like
> [FindBugs|http://findbugs.sourceforge.net] can use them to look for threading
> problems more easily and widely.
> A downside is that the annotations include a compile-time Maven dependency
> (which could be worked around with optional scoping, for example).
> This ticket would only be for adding the JCIP dependency so that the
> annotations are available for future work, and specifically not applying them
> to existing code right now.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
