[
https://issues.apache.org/jira/browse/AVRO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077433#comment-18077433
]
ASF subversion and git services commented on AVRO-4251:
-------------------------------------------------------
Commit 29ce04d9fafdf560391e0cdc2076b9dbc0a78ee1 in avro's branch
refs/heads/avro-4251-japicmp-backwards-compatibility from Ismaël Mejía
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=29ce04d9fa ]
AVRO-4251: [Java] Validate backwards compatibility issues with japicmp
> [Java] Validate backwards compatibility issues with japicmp
> -----------------------------------------------------------
>
> Key: AVRO-4251
> URL: https://issues.apache.org/jira/browse/AVRO-4251
> Project: Apache Avro
> Issue Type: Improvement
> Components: build
> Reporter: Ismaël Mejía
> Assignee: Ismaël Mejía
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Given how critical is Java API compatibility for the downstream ecosystem we
> should add a backwards compatibiliy check as part of the build system. The
> Avro Java implementation has never guaranteed full backwards compatibility
> but we have cared to rarely break it. With this if we decide to improve the
> APIs at least we can track the reasoning.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
