Skip to content
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

Improve Surefire setup to avoid dynamic agent agent attachment warning #1034

Closed
odrotbohm opened this issue Jan 23, 2025 · 0 comments
Closed
Assignees
Labels
in: infrastructure Build / CI / Release type: task General tasks
Milestone

Comments

@odrotbohm
Copy link
Member

Back-port of GH-1033.

@odrotbohm odrotbohm added in: infrastructure Build / CI / Release type: task General tasks labels Jan 23, 2025
@odrotbohm odrotbohm added this to the 1.3.3 milestone Jan 23, 2025
@odrotbohm odrotbohm self-assigned this Jan 23, 2025
odrotbohm added a commit that referenced this issue Jan 23, 2025
Prior to this commit, running our tests caused the following warning because Mockito was dynamically self-attaching to the running JVM:

Mockito is currently self-attaching to enable the inline-mock-maker. This will no longer work in future releases of the JDK. Please add Mockito as an agent to your build what is described in Mockito's documentation: https://javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/Mockito.html#0.3

We now follow the advice in the provided link and set up our build accordingly.
odrotbohm added a commit that referenced this issue Jan 27, 2025
This reverts commit 003c428. See [0] for details. Additionally, the change causes our integration builds to fail as the Mockito versions referred to by older Boot versions do not contain the necessary manifest entries.

[0] eclipse-m2e/m2e-core#1916 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: infrastructure Build / CI / Release type: task General tasks
Projects
None yet
Development

No branches or pull requests

1 participant