Skip to content

Support Byte-Buddy / Mockito with JDK 23 via -Dnet.bytebuddy.experimental=true #414

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2024

Conversation

rob-bygrave
Copy link
Contributor

No description provided.

@SentryMan SentryMan enabled auto-merge April 9, 2024 02:52
@SentryMan SentryMan merged commit 5c5ad58 into master Apr 9, 2024
5 checks passed
@rob-bygrave rob-bygrave deleted the feature/jdk-23-mockito-byte-buddy branch April 9, 2024 02:54
@rob-bygrave
Copy link
Contributor Author

Its very tempting to include this "fix" / maven-surefire-plugin configuration in the parent pom. So more like:

  • Update io.avaje:junit to include the latest for mockito and byte-buddy
  • Update the parent pom to have this configuration for maven-surefire-plugin and maven-failsafe-plugin enabled by default

@SentryMan
Copy link
Collaborator

  • Update io.avaje:junit to include the latest for mockito and byte-buddy

I'd add dependabot to it but I don't know where avaje-junit is

@SentryMan
Copy link
Collaborator

checks notes It seems that avaje-junite merely aggregates some common testing libs. Do you think we would get better mileage by directly declaring and letting dependabot take care of things?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants