Skip to content

Alternate backport of demos update#3317

Draft
chrisdennis wants to merge 2 commits intoehcache:release/3.11from
chrisdennis:demos-backport-review
Draft

Alternate backport of demos update#3317
chrisdennis wants to merge 2 commits intoehcache:release/3.11from
chrisdennis:demos-backport-review

Conversation

@chrisdennis
Copy link
Member

No description provided.

aurbroszniowski and others added 2 commits March 5, 2026 10:35
…) and add slf4j exclusions on Terracotta dependencies (statistics, offheap-store, sizeof, terracotta-utilities-tools) that declare the conflicting 1.7 range

- Fix Java deprecation/removal warnings treated as errors by -Werror
- Add missing javax.xml.bind:jaxb-api to xjcToolJakarta configuration to fix ClassNotFoundException during Jakarta XJC code generation
- Add javadocAdd/jakartaJavadocAdd classpath configurations in ehcache/build.gradle (spotbugs-annotations, jaxb-api) and clustered/ehcache-clustered/build.gradle (ehcache-common-api, ehcache-common) required for javadocJar tasks in the assemble chain
- Backport of TDB-19854 (master/3.12): upgrade SpotBugs to 4.9.8, AssertJ to 3.27.7, Mockito to 5.12.0, ByteBuddy to 1.18.3; rewrite demos to use embedded Jetty 12 instead of Gretty; refactor SPI tests to use JUnit 4 rules; update Mockito 5 API usage (MockitoAnnotations, ArgumentMatchers); fix SpotBugs annotation usages
- Address compilation errors and test failures introduced by upgrading slf4j from 1.7.x to 2.0.17
- PR build with java 17
- Fix async assertion (implemented manually since awaitility is not present)
Copy link
Contributor

@aurbroszniowski aurbroszniowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR makes sense, just a couple of points:

  • Shouldn't we keep the @SuppressWarnings from my PR? It wouldn't have a negative impact and would get rid of compilation errors (not blocking in java 8 but blocking for someone who wants to compile with java 17)
  • same for the deprecation fix in my PR about newInstance(); replaced by .getDeclaredConstructor().newInstance()
  • Also shouldn't we keep the expectExceptionhelper inSPIStoreTester from my PR? It doesn't impact negatively the build, and makes the test code more readable

@@ -0,0 +1,55 @@
/*
* Copyright Terracotta, Inc.
* Copyright IBM Corp. 2024, 2025
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to move this to 2026 now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet