[
https://issues.apache.org/jira/browse/CALCITE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188306#comment-15188306
]
Julian Hyde commented on CALCITE-1144:
--------------------------------------
bq. On the contrary, the jars that we deploy to Maven central do constitute a
binary release.
Never thought of it as such, but you're right. I agree that the protobuf stuff
needs to be in the LICENSE of the JAR. Is there an easy way to use a different
LICENSE/NOTICE for a particular JAR?
bq. As such, that's why I don't think the L&N for our source release needs it.
Agreed.
> Fix Avatica LICENSE file
> ------------------------
>
> Key: CALCITE-1144
> URL: https://issues.apache.org/jira/browse/CALCITE-1144
> Project: Calcite
> Issue Type: Sub-task
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.7.0
>
>
> Needs to say "Apache Calcite Avatica Sub Components" not "Apache Calcite Sub
> Components".
> Also, placeholder for concern about missing jekyll/sass entries from Julian.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
