You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2020/03/25 09:58:00 UTC

[jira] [Commented] (CALCITE-3871) Remove dependency of org.apiguardian:apiguardian-api

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

Stamatis Zampetakis commented on CALCITE-3871:
----------------------------------------------

With this change every Calcite module that needs to annotate its APIs needs to include a dependency in linq4j, thus I am not sure if copying the class there is a better option. 

> Remove dependency of org.apiguardian:apiguardian-api
> ----------------------------------------------------
>
>                 Key: CALCITE-3871
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3871
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core, linq4j
>    Affects Versions: 1.22.0
>            Reporter: Danny Chen
>            Assignee: Danny Chen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.23.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The org.apiguardian:apiguardian-api is introduced in CALCITE-3652 in order to mark the new introduced API status.
> Remove the dependency and copy the class into Calcite because the org.apiguardian:apiguardian-api jar has only a single API.java class and it is not necessary to add a dependency for that(All the downstream projects that have calcite-core as a dependency would see this jar which is annoying).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)