[JIRA] (JENKINS-61279) Update version number dependency to 1.7

[timjacomb1@gmail.com (JIRA)]

Tim Jacomb created an issue

Jenkins / JENKINS-61279 Update version number dependency to 1.7 Issue Type: New Feature Assignee: Unassigned Components: core Created: 2020-02-29 14:47 Priority: Minor Reporter: Tim Jacomb Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[timjacomb1@gmail.com (JIRA)]

Tim Jacomb started work on JENKINS-61279

Change By: Tim Jacomb Status: Open In Progress

Add Comment

[timjacomb1@gmail.com (JIRA)]

Tim Jacomb updated JENKINS-61279

Jenkins / JENKINS-61279 Update version number dependency to 1.7

Change By: Tim Jacomb Status: In Progress Review

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated JENKINS-61279

Jenkins / JENKINS-61279 Update version number dependency to 1.7

Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.224

Add Comment

[timjacomb1@gmail.com (JIRA)]

Tim Jacomb updated an issue

Jenkins / JENKINS-61279 Update version number dependency to 1.7

Change By: Tim Jacomb Labels: lts-candidate

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-61279

Re: Update version number dependency to 1.7 Tim JacombIf you label an issue lts-candidate, you should make sure its issue type doesn't disqualify it from backporting: https://issues.jenkins-ci.org/issues/?filter=12146

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck updated an issue

Jenkins / JENKINS-61279

Update version number dependency to 1.7

Change By: Daniel Beck Issue Type: New Feature Improvement

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža updated an issue

Jenkins / JENKINS-61279 Update version number dependency to 1.7

Change By: Oliver Gondža The library changes https://github.com/jenkinsci/lib-version-number/compare/version-number-1.6...version-number-1.7

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža commented on JENKINS-61279

Re: Update version number dependency to 1.7 Tim Jacomb, how does the deprecation manifests? It is a build warning for plugins depending on affected core version?

Add Comment

[timjacomb1@gmail.com (JIRA)]

Tim Jacomb commented on JENKINS-61279

Re: Update version number dependency to 1.7

This is for CheckNonNull, Nullable etc, without this change when you increase your minimum core version you pick up a version of spotbugs that has deprecated the annotations that don't violate the javax license. When we increased the configuration-as-code baseline to ~2.220 we got 50+ deprecation warnings due to this, this one line lib bump fixes it for plugins without any workaround on the plugin side having to mess around excluding core dependencies

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža commented on JENKINS-61279

Re: Update version number dependency to 1.7

Tim Jacomb, thanks. Though since this only affects plugin build and not its executions and (as I understood) it does not even prevent the static analysis to detect problems, I still lean towards not to add this.

Add Comment

[timjacomb1@gmail.com (JIRA)]

Tim Jacomb commented on JENKINS-61279

Re: Update version number dependency to 1.7

It's more that it's annoying and wastes time for the plugin developer whose IDE is complaining about all these deprecation warnings after bumping the minimum required core version, and has to go investigate them, it's a waste of time IMO.

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža updated an issue

Jenkins / JENKINS-61279

Update version number dependency to 1.7

Change By: Oliver Gondža Labels: lts 2.222.2 - candidate fixed

Add Comment