[jira] [Updated] (CALCITE-4061) Build should fail if Calcite code uses deprecated APIs

["Vladimir Sitnikov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CALCITE-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Sitnikov updated CALCITE-4061:
---------------------------------------
    Fix Version/s: 1.24.0

> Build should fail if Calcite code uses deprecated APIs 
> -------------------------------------------------------
>
>                 Key: CALCITE-4061
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4061
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Vladimir Sitnikov
>            Priority: Major
>             Fix For: 1.24.0
>
>
> Calcite build should fail if Calcite code uses deprecated APIs. This includes external APIs (e.g. Guava methods) and internal APIs (e.g. a deprecated class in the org.apache.calcite.util package).
> This used to occur when the build was powered by Maven.
> Compared to a policy where code is allowed to use deprecated APIs for a 'grace period', this policy has a number of advantages. One is that Calcite devs (or users) can upgrade dependencies at short notice, with no code changes.
> Another is that it forces people who are doing internal refactoring (replacing one internal Calcite API with another) to finish the job.
> [~vlsi] Can you take this please? I can't figure out how to set javac's '-Xlint:deprecated -Werror' from Gradle.



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