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

[JENKINS-55456] Upgrade PowerMock version to 2.0.0 #148

Merged
merged 1 commit into from
Jan 28, 2019

Conversation

alecharp
Copy link
Member

@alecharp alecharp commented Jan 8, 2019

JENKINS-55456

Upgrade powermock Junit and Mockito libraries from 2.0.0-RC.4 to 2.0.0.

Copy link

@Wadeck Wadeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release note: 2.0.0 <-> 2.0.0-RC.4

Note as "enhancement", they remove some deprecated code parts issue 839. That could potentially lead to some regressions.

@batmat batmat self-requested a review January 9, 2019 08:52
@batmat
Copy link
Member

batmat commented Jan 9, 2019

Please file downstream PRs on some critical plugins to assess this using a timestamped SNAPSHOT, ideally plugins using powermock.
See #137 for an example on the Git-plugin.

From a cursory look, it would look like a passing PR on both git-plugin and blueocean-plugin repos would be enough to detect potential/immediate regressions as noted by Wadeck.

Thanks!

@batmat batmat added the needs-downstream-pr Used when a PR should be filed on (some) plugins to show the change does not introduce regressions label Jan 9, 2019
@@ -205,12 +205,12 @@
<dependency>
<groupId>org.powermock</groupId>
<artifactId>powermock-module-junit4</artifactId>
<version>2.0.0-RC.4</version>
<version>2.0.0</version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it was a complete shock to me that this was even included - personally I feel neither mocito nor powermock should be in here and it is up to the individual plugins to use them if they desire.

for example if a new plugin includes a test project from a plugin built with older parent the dependency will automatically be shunted and is liable o break things.

/shrug

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's in the dependencyManagement. So we don't force anyone to use them, just we put a recommended version, so plugins can add those dependencies in their pom.xml without a version.

Also, if any plugin wants a different version, they can put a version to use and this will be ignored.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it was deliberate since we have got a lot of fun while testing with Java 11

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, if any plugin wants a different version, they can put a version to use and this will be ignored

for an individual plugin yes, but if another plugin depends on that plugin no, the dependency gets overridden

@batmat
Copy link
Member

batmat commented Jan 11, 2019

Ping @alecharp.
BTW if you need help on how to create such "downstream PRs", you know how to reach out to me :-).

Have a great weekend!

@alecharp
Copy link
Member Author

@batmat I'm working on the PR for blueocean-plugin but the project already has a <dependencyManagement/> for PowerMock and Mockito. I'm not sure they will agree to remove them. I'm opening a PR anyway.

alecharp added a commit to alecharp/blueocean-plugin that referenced this pull request Jan 16, 2019
This is to validate jenkinsci/plugin-pom#148 and the fact that PowerMock 2.0.0
is not breaking plugins' validation process.
@oleg-nenashev
Copy link
Member

🚢 🇮🇹 ?

@alecharp
Copy link
Member Author

It seems that the PR in Git Plugin is building correctly. See jenkinsci/git-plugin#662. Maybe we could merge this.

@batmat batmat added java and removed needs-downstream-pr Used when a PR should be filed on (some) plugins to show the change does not introduce regressions labels Jan 28, 2019
@oleg-nenashev oleg-nenashev merged commit ec47379 into jenkinsci:master Jan 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants