Dropwizard 2.0.25 -> 2.0.26 dependency issue causing surefire errors
See original GitHub issueWe recently tried upgrading from 2.0.25 to 2.0.26 and some of our maven modules fail to compile with this error:
Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test
org.apache.maven.surefire.booter.SurefireBooterForkException: There was an error in the forked process
Any idea what dependency changes might be related to this?
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Upgrade Notes for Dropwizard 2.0.x
dropwizard :dropwizard-bom artifact only specifies the versions of the official Dropwizard modules but no transitive dependencies anymore. If you want to pin the ......
Read more >Failed to execute goal org.apache.maven.plugins:maven ...
In your error code he didn't find surefire plugin so add it ... will try to automatically configure application according to dependencies in...
Read more >org.springframework.boot:spring-boot: Versions | Openbase
isWrapperFor with a class rather than an interface causing Oracle UCP ... Signed jar dependency performance problem when repackaged in a single jar...
Read more >dropwizard-core - Maven Repository
Version Vulnerabilities Repository Usages Date
4.0.x 4.0.0‑beta.3 Central 9 Oct 12, 2022
4.0.0‑beta.2 4.0.x Central 10 Jun 30, 2022
4.0.0‑beta.1 4.0.x Central 12 Apr 09, 2022...
Read more >dropwizard - bytemeta
Dropwizard 2.0.25 -> 2.0.26 dependency issue causing surefire errors ... Make software development more efficient, Also welcome to join our telegram.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve opened a ticket with surefire plugin here https://issues.apache.org/jira/browse/SUREFIRE-1971
I just tested this and when using the
maven-surefire-plugin
with version3.0.0-M5
there seems to be an issue with the Jersey client:However, this is just an error in the logs and the tests run fine. I just don’t know, if this could fail on different JDKs or Maven versions.
This issue persists in the latest beta of 2.1.0 too, so I think we shouldn’t update that fast to surefire-plugin version 3.