[
https://issues.apache.org/jira/browse/CALCITE-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176457#comment-15176457
]
Josh Elser commented on CALCITE-1111:
-------------------------------------
+1 works for me since we're taking on the testing burden. Clear documentation
on building Calcite is nice -- do you think downstream consumers of Calcite
will understand that they can just do the following in their own Maven pom, or
do we need to be painfully specific?
{code}
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>${whatever_version_you_want_in_advertised_range}</version>
</dependency>
{code}
> Upgrade Guava, and test on a range of Guava versions
> ----------------------------------------------------
>
> Key: CALCITE-1111
> URL: https://issues.apache.org/jira/browse/CALCITE-1111
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Cassandra server depends on Guava 15.0. To use it we'd need to upgrade Guava
> too. But Hive is still on Guava 14, as is the rest of Hadoop.
> It might just work if we upgrade Calcite to Guava 15.0 but mark the
> dependency "provided". Then Hive can continue to provide Guava 14. It should
> give other projects more flexibility too.
> We should continue to run on versions of Guava as early as 11, and also try
> running on recent versions (the latest is 19). We should describe the
> dependencies in http://calcite.apache.org/downloads/#maven-artifacts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
