[
https://issues.apache.org/jira/browse/CALCITE-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071290#comment-17071290
]
Jiahui Jiang commented on CALCITE-3888:
---------------------------------------
avatica-server used to be just a [test dependency for
calcite-core|[https://github.com/apache/calcite/blob/calcite-1.21.0/core/pom.xml#L52]]
but now an
[implementation|[https://github.com/apache/calcite/blob/ebbba566fbdbdd0923adda596467090d708cc14b/core/build.gradle.kts#L55]]
dependency.
We are depending on calcite only for the parser function so was surprised that
after upgrading it started to bring in avatica-server
> 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)
