Thanks, Anil.
I will do as you suggest.
Alberto
________________________________
From: Anilkumar Gingade <aging...@vmware.com>
Sent: Tuesday, November 23, 2021 7:33 PM
To: dev@geode.apache.org <dev@geode.apache.org>
Subject: Re: API check error when adding a new method to a public interface
Alberto,
I don’t think the intention is to avoid, discourage adding a new method...As
you have seen any changes to the API or adding a new API has implications on
other parts of the product, it is good to validate/verify and address the
dependency across the product and get everything working in accordance (without
breaking any compatibility). If you have any requirement please propose through
RFC and get an approval.
-Anil.
On 11/23/21, 8:44 AM, "Alberto Gomez" <alberto.go...@est.tech> wrote:
Hi,
After the introduction of GEODE-9702
(https://issues.apache.org/jira/browse/GEODE-9702), adding a new method to a
public interface will make the api-check-test-openjdk11 fail even if a default
implementation is provided.
My question is if the goal of this change is to forbid this type of changes
in minor versions or if there is a process to follow in order for changes of
this type to be added.
I wanted to propose (in an RFC) the addition of a new parameter to the
create gateway sender command that would require adding a new method to the
GatewaySender interface as well as to other public interfaces and I was
wondering if this will be possible at all, and if so, how should I proceed with
it.
Thanks,
Alberto
