Open
Conversation
build: update plugins and dependencies build: clean up gradle configuration files
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.
Summary of Changes
Dependency Updates
Updated plugins and core dependencies, including:
5.x->6.2.12.+->3.0.26.2.0.RELEASE->6.2.7.RELEASEThese updates resolved the following Snyk vulnerabilities:
TBA
Dependency Cleanup & Fixes:
io.lettuce:lettuce-coreto6.2.7.RELEASE, which natively resolves CVE-2022-41915 (Netty vulnerability). This allowed for the removal of the manualio.netty:netty-handlerversion override in:store-redis.Gradle Project Improvements
This PR aligns the
path-facilitiesconfiguration with the modern architectural standards recently established inpath-coreandpath-mdx-model.Root Project (
build.gradle)testImplementation "com.mx.path-core:testing"into the rootsubprojectsblock so all facility modules natively inherit the standardized test framework.subprojectsblock. (Also fixed a legacy copy-paste bug where the POM URL incorrectly pointed topath-core).pathSDKVersiontopathCoreVersionand bumped the range to[6.0,7.0)to align with the core ecosystem.afterEvaluateblocks forspotlessApplyandsubdependencieswith lazy task configuration.sourceCompatibilityandtargetCompatibilityby enforcing Java 17 globally using the modernjava { toolchain { ... } }API.sourcesJar,packageJavadoc) with the nativejava { withSourcesJar(); withJavadocJar() }DSL.Sub-Projects (
store-redis,store-vault,message-broker-nats, etc.)commons-codecandslf4jlibraries, allowing them to strictly inherit the centralized coordinates from thepath-coreBOM constraints.mockito-inline,spock-core, andslf4j-simpleacross all sub-projects. These are now provided seamlessly by root inheritance and the modernizedpath-core:testingAPI.extvariable block infault-tolerant-executor-resilience4jto explicitly useproject.ext.resilience4jVersionfor safer scope resolution.excludePreReleaseVersions = truelines from localcoppuccinoblocks, as this is now handled centrally.Platform BOM (
platform)pom { ... }metadata blocks and manual signing tasks. The project now strictly acts as ajava-platformto cleanly expose thepath-facilitiesconstraints to external consumers.Public API Additions/Changes
N/A
Downstream Consumer Impact
N/A
How Has This Been Tested?
Verified that the BOM generates correctly, dependencies resolve cleanly, and vulnerabilities are minimized by running
snyk test --all-projects --exclude=build.Snyk scan results
Checklist: