You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vadim Pakhnushev (Jira)" <ji...@apache.org> on 2025/10/09 08:39:00 UTC

[jira] [Assigned] (IGNITE-26511) Improve Java API compatibility check

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

Vadim Pakhnushev reassigned IGNITE-26511:
-----------------------------------------

    Assignee: Vadim Pakhnushev

> Improve Java API compatibility check
> ------------------------------------
>
>                 Key: IGNITE-26511
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26511
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Iurii Gerzhedovich
>            Assignee: Vadim Pakhnushev
>            Priority: Major
>              Labels: ignite-3, release-3.1.0-blocker
>
> The Java API compatibility check introduced in IGNITE-24458 has several significant flaws that need to be addressed.
> What are the issues:
>  # Exclusion is possible only on the Class level instead of methods for some cases, as example, when changing the return type for a method. This approach leads to new problems in these classes being ignored and not noticed.
>  # The test structure always tests the master against a bunch of versions with the same list of suppressors. This means:
>  ** In 3.1.0, broke API compatibility somewhere by adding an exclude clause.
>  ** The same exclude clause will be applied when testing compatibility between 3.3.0 and 3.2.0 in the future. This is wrong. An exclusion clause should have a limited scope.
>  # 
> The release process should be aware of any actions required to continue supporting
> the compatibility. All required actions should be reflected in RELEASE.md



--
This message was sent by Atlassian Jira
(v8.20.10#820010)