upgrading junit-jupiter fails due to invalid Gradle build config
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 39/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system, testing
Research direction
Start with the junit configuration in the pulsar-client-reactive build and compare it with the linked Gradle discussion. Reproduce the failure while upgrading junit-jupiter, then verify that the corrected configuration allows the upgrade and the existing test build passes.
Written by the indexing model from the issue text.
Description
The junit configuration in the pulsar-client-reactive build isn't correct so upgrading junit-jupiter fails. I reverted that part. (this solution seems to work for fixing the issue with junit-jupiter upgrade).
Originally posted by @lhotari in https://github.com/apache/pulsar-client-reactive/issues/225#issuecomment-2961931080
- Dominant language
- Java
- Stars
- 67
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/pulsar-client-reactive
-
Acknowledge outside of consumeMany and consumeOneMay be free again @lhotari claimed this 512 days ago, and no pull request is open. Open
apache/pulsar-client-reactive#220 · 1 comment · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
apache/pulsar-client-reactive#216 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apache/pulsar-client-reactive#182 ·
-
Add support for MutinyMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apache/pulsar-client-reactive#114 · 6 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in apache/pulsar-client-reactive
Similar issues
-
human-required sync-failed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/osdu-spi-file#63 ·
Maintainers usually reply within 1 day
-
frontend quick win
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CodeForPhilly/benefit-decision-toolkit#571 ·
Maintainers usually reply within 1 day
-
approved
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
checkstyle/checkstyle#22129 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Add Hardcharger JDBC driverPossibly taken @prmoore77 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day