-
-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
💣 Remove powermock #5736
💣 Remove powermock #5736
Conversation
@@ -478,7 +478,7 @@ private void checkTarUntarRoundTrip(String filePrefix, long fileSize) throws Exc | |||
} | |||
|
|||
@Test public void copyToWithPermissionSpecialPermissions() throws IOException, InterruptedException { | |||
assumeFalse("Test uses POSIX-specific features", Functions.isWindows()); | |||
assumeFalse("Test uses POSIX-specific features", Functions.isWindows() || Platform.isDarwin()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fails on my mac, assume fine to skip it there
014219f
to
f075fd1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like an improvement. I would not mind deleting all the Mockito tests too, but that is another matter.
Recommend also removing the dependency management entry from the plugin POM.
Won't that break plugins using powermock when they upgrade to that parent POM? Or is that an intentional outcome of what you're proposing so that plugin maintainers are notified that core no longer uses powermock? |
IIRC powermock was originally added to the plugin parent pom to try get people on at least java 11 compatible versions, although it was never really compatible with java 11 you had to add a whole bunch of hacks / workarounds to make it work. This would be a you should really remove your powermock tests, either migrate to mockito, integration tests, facade pattern or just remove the tests entirely |
I can reproduce the last failure with
|
5e48ec6
to
c836091
Compare
Removal from the plugin pom proposed in jenkinsci/plugin-pom#442, but shouldn't affect this PR For the record this PR changes the failing test count on Java 17: Before:
Now:
Remaining failures are xstream related which will likely require surefire args changes or changing the default converter with xstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally I prefer PowerMock to Mockito. I hope it is a matter of time until PowerMock is adapted though it is likely to be a breaking change too. No objections from me w.r.t this PR, +1
We may merge it in 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process |
It doesn't work on Java 17 as far as I can tell, at least with some basic effort, and it appears to be unmaintained.
Mockito can do what it was doing generally.
some tests I couldn't get working or were too painful =/
cc @jglick