[
https://issues.apache.org/jira/browse/CALCITE-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799352#comment-15799352
]
Josh Elser commented on CALCITE-1562:
-------------------------------------
https://lists.apache.org/thread.html/f229214afd75e07017c0ae17f1d23244946b2ba2fefbd1526427450c@%3Cdev.fluo.apache.org%3E
was the email I was thinking of.
The lineage of jsr305 from google code making it to
https://github.com/amaembo/jsr-305 is also a little sketchy (do we know if this
is actually the same author?). Personally, it's the sum of this ambiguity and
the ease of a replacement which pushes me into the "just replace it" mindset.
> Switch com.google.code.findbugs:jsr305 to
> com.github.stephenc.findbugs:findbugs-annotations
> -------------------------------------------------------------------------------------------
>
> Key: CALCITE-1562
> URL: https://issues.apache.org/jira/browse/CALCITE-1562
> Project: Calcite
> Issue Type: Task
> Components: core
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.12.0
>
>
> The licensing on com.google.code.findbugs:jsr305 is rather murky. It would be
> trivial to switch over to using
> com.github.stephenc.findbugs:findbugs-annotations which is clearly licensed
> and provides the same functionality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
