Repository navigation
Merge pending 0.14.x changes into main branch - #1056
Merged
Merged
Conversation
- Upgraded dependencies and maven plugins to latest versions compatible with JDK 8+. - Remove JDK 7 from CI build - Consolidated `ci.yml` build matrix - JDK 8 through 24 build testing - Removed `io.jsonwebtoken.impl.lang.Function` in favor of `java.util.function.Function` - Marked API interfaces as `@FunctionalInterface` where possible - Migrated `io.jsonwebtoken.lang.Supplier` usages to `java.util.function.Supplier` where possible, except for `RedactedSupplier` usages. - Breaking change: Renamed and moved `io.jsonwebtoken.lang.Supplier` to `io.jsonwebtoken.security.ConfidentialValue` - Breaking change: Renamed `GsonSupplierSerializer` to `GsonConfidentialValueSerializer` - Breaking change: Renamed `JacksonSupplierSerializer` to `JacksonConfidentialValueSerializer` * Declared `@FunctionalInterface` / cleanup where feasible. * Removing explicit Java 7 and Java 8 callouts/references now that 8 is the default/baseline. * Removing explicit Java 7 and Java 8 callouts/references now that 8 is the default/baseline. * Minor JavaDoc enhancement
…a 17 (#1046) Drop JDK 7, raise minimum JRE to Java 8, and minimum build JDK to Java 17: - Remove all JDK 7 maven source/target compatibility settings - Raise minimum required Java runtime from 7 to 8 - Set build JDK to 17; update CI to use JDK 17 for code-coverage job - Make jdk-17 test profile active by default - Replace -P jdk-N activation with -Dtest.jdk.version=N property: Each jdk-N profile now activates via test.jdk.version=N property value instead of requiring -P on the command line. A companion profile skip-default-tests suppresses the default surefire execution whenever test.jdk.version is set, so only the requested JDK runs tests. Default build (no property): default-test runs on the build JDK. Targeted run: ./mvnw test -Dtest.jdk.version=8|11|17|21|25 CI shape becomes uniform across all JDK matrix entries. * Java 8 API compatibility changes (#1015): - Upgraded dependencies and maven plugins to latest versions compatible with JDK 8+. - Remove JDK 7 from CI build - Consolidated `ci.yml` build matrix - JDK 8 through 25 build testing - Removed `io.jsonwebtoken.impl.lang.Function` in favor of `java.util.function.Function` - Marked API interfaces as `@FunctionalInterface` where possible - Migrated `io.jsonwebtoken.lang.Supplier` usages to `java.util.function.Supplier` where possible, except for `RedactedSupplier` usages. - Breaking change: Renamed and moved `io.jsonwebtoken.lang.Supplier` to `io.jsonwebtoken.security.ConfidentialValue` - Breaking change: Renamed `GsonSupplierSerializer` to `GsonConfidentialValueSerializer` - Breaking change: Renamed `JacksonSupplierSerializer` to `JacksonConfidentialValueSerializer` - Declared `@FunctionalInterface` / cleanup where feasible. - Removing explicit Java 7 and Java 8 callouts/references now that 8 is the default/baseline. * use release for m-compiler-p and m-javadoc-p # (#1019) * Add tests to reach 100% Clover coverage; run coverage job on JDK 17: - Cover previously-uncovered branches in ProviderKey, ProviderPrivateKey, ProvidedPrivateKeyBuilder, KeysBridge, and JcaTemplate.JcaInstanceFactory. - On macOS these branches are only exercised by Pkcs11Test (which fails locally due to a SoftHSM2/SunPKCS11 ECDSA incompatibility), so explicit unit tests are added to cover them on all platforms. - Switch the CI code-coverage job to JDK 17, and remove the now-unnecessary 'sleep 90s' workaround. - changed surefire plugin deprecated `forkMode` usages to replacement forkCount/reuseForks equivalents. - Specified surefire.argLine property for surefire runs, with an empty value for JDK 8 (since not supported on 8) * Update CI build matrix Java versions (#1053) - Runs each job JDK version in parallel - uses `test.jdk.version` to remove _default_ execution of test (only running the matrix target tests) * Extract repetitive CI setup steps into a composite action (#1054): Consolidate checkout, setup-java, setup-maven, and SoftHSM steps into a reusable local composite action under `.github/actions/`. This will help simplify maintenance and future action version updates. - Pin GitHub Actions to commit SHAs: Use immutable commit SHAs for checkout, setup-java, and setup-maven actions: https://docs.github.com/en/actions/reference/security/secure-use#using-third-party-actions --------- Co-authored-by: Brian Demers <bdemers@apache.org> Co-authored-by: Benjamin Marwell <bmarwell@apache.org> Co-authored-by: Ignacio Piñeyro <juanpineyrob@gmail.com> Co-authored-by: Les Hazlewood <121180+lhazlewood@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.