ENHANCEMENT: bump junit.version from 5.11.4 to 5.12.2 + clean up
Pull Request Template
What does this PR do?
- Upgrading JUnit to version 5.12.2.
- Replacing individual dependencies (
junit-jupiter-engineandjunit-jupiter-params) with thejunit-jupiteraggregator package https://mvnrepository.com/artifact/org.junit.jupiter/junit-jupiter - Moving
mockito-junit-jupiterdependency to the parentpom.xmlas it was previously declared with explicit versions in some modules. Also, excludingjunit-jupiter-apifrom this dependency since the latestmockito-junit-jupiterversion includes older version ofjunit-jupiter-api, which was causing test failures. - Refactoring
SimpleFileWriterTestto be compatible with JUnit 5.
Fixes https://github.com/iluwatar/java-design-patterns/pull/3259
⏳ Analyzing changes in this PR... ⏳
This might take a few minutes, please wait
📥 Commits
Analyzing changes from base (8a64f4c) to latest commit (afe3910):
📁 Files being considered (30)
🔄 abstract-document/pom.xml (1 hunk) 🔄 abstract-factory/pom.xml (1 hunk) 🔄 active-object/pom.xml (1 hunk) 🔄 actor-model/pom.xml (1 hunk) 🔄 acyclic-visitor/pom.xml (1 hunk) 🔄 adapter/pom.xml (1 hunk) 🔄 ambassador/pom.xml (1 hunk) 🔄 anti-corruption-layer/pom.xml (1 hunk) 🔄 arrange-act-assert/pom.xml (1 hunk) 🔄 async-method-invocation/pom.xml (1 hunk) 🔄 backpressure/pom.xml (1 hunk) 🔄 balking/pom.xml (1 hunk) 🔄 bloc/pom.xml (1 hunk) 🔄 bridge/pom.xml (1 hunk) 🔄 builder/pom.xml (1 hunk) 🔄 business-delegate/pom.xml (1 hunk) 🔄 bytecode/pom.xml (1 hunk) 🔄 caching/pom.xml (1 hunk) 🔄 callback/pom.xml (1 hunk) 🔄 chain-of-responsibility/pom.xml (1 hunk) 🔄 circuit-breaker/pom.xml (1 hunk) 🔄 clean-architecture/pom.xml (1 hunk) 🔄 client-session/pom.xml (1 hunk) 🔄 collecting-parameter/pom.xml (1 hunk) 🔄 collection-pipeline/pom.xml (1 hunk) 🔄 combinator/pom.xml (1 hunk) 🔄 command-query-responsibility-segregation/pom.xml (1 hunk) 🔄 command/pom.xml (1 hunk) 🔄 commander/pom.xml (1 hunk) 🔄 component/pom.xml (1 hunk)
autogenerated by presubmit.ai
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
hi @iluwatar,
I'm not sure how Presubmit.ai determines the PR type. I've updated the PR title - would re-triggering the job resolve the issue, or should I update the commit messages instead?
This PR is stale because it has been open 60 days with no activity.
Its pending review
This PR is stale because it has been open 60 days with no activity.