What’s going on with CI now? I’m not impressed by a random Windows failure
breaking the entire build, especially one that’s apparently been failing for a
while apparently. Dependabot??
—
Matt Sicker
> Begin forwarded message:
>
> From: Matt Sicker
> Subject: [apache/logging-log4j2] Run failed:
There’s @Deprecated(forRemoval = true) which can rise different warnings or
errors from a regular deprecated element.
—
Matt Sicker
> On May 13, 2022, at 16:32, Ralph Goers wrote:
>
> I believe we moved the things in Foo2, Foo3, etc to the parent as default
> methods
> but left empty interfac
I believe we moved the things in Foo2, Foo3, etc to the parent as default
methods
but left empty interfaces or classes in their place so that compatibility
wouldn’t be broken.
In an ideal world it would be nice to have a way to prevent them from being
used
when compiling. Perhaps an annotation
I certainly would hope that collapsing Foo2, Foo3 into their parent is up
for consideration for 3.0. Memories of Microsoft COM and DCOM...
Gary
On Fri, May 13, 2022, 13:36 Matt Sicker wrote:
> The only realistic way to break compatibility in the API is to
> introduce a v3 API and make the v3 Co
The only realistic way to break compatibility in the API is to
introduce a v3 API and make the v3 Core implement both the v2 and v3
APIs (or breaking that into two modules, but that introduces more log
bridge confusion which is already a huge mess thanks to people
continually reinventing logging AP
