[
https://issues.apache.org/jira/browse/CALCITE-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071261#comment-17071261
]
Vladimir Sitnikov commented on CALCITE-3888:
--------------------------------------------
What is the issue exactly?
Apparently avatica-server exposes jetty-server classes in the API, and
calcite-core depends on avatica-server. That requires to have jetty-server on
the compile classpath.
> Exclude jetty-server from core's compileClasspath
> -------------------------------------------------
>
> Key: CALCITE-3888
> URL: https://issues.apache.org/jira/browse/CALCITE-3888
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.22.0
> Reporter: Jiahui Jiang
> Priority: Major
>
> After moving to gradle, core starts to have compile dependency on
> jetty-server, which was [not the case
> pre-1.21.0|http://[https://github.com/apache/calcite/blob/calcite-1.21.0/core/pom.xml#L405]].
> Downstream users using calcite-core can bring in jetty-server dependencies
> accidentally. It should be excluded from compile dependency
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
