Skip to content

Apply staticanalysis.RemoveUnusedPrivateMethods#10962

Closed
Pankraz76 wants to merge 1 commit intojenkinsci:masterfrom
Pankraz76:rw-apply
Closed

Apply staticanalysis.RemoveUnusedPrivateMethods#10962
Pankraz76 wants to merge 1 commit intojenkinsci:masterfrom
Pankraz76:rw-apply

Conversation

@Pankraz76
Copy link

See JENKINS-XXXXX.

Testing done

Proposed changelog entries

  • human-readable text

Proposed changelog category

/label

Proposed upgrade guidelines

N/A

Submitter checklist

  • The Jira issue, if it exists, is well-described.
  • The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
  • There is automated testing or an explanation as to why this change has no tests.
  • New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
  • New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
  • New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
  • For dependency updates, there are links to external changelogs and, if possible, full differentials.
  • For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

  • There are at least two (2) approvals for the pull request and no outstanding requests for change.
  • Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
  • Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
  • Proper changelog labels are set so that the changelog can be generated automatically.
  • If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
  • If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

@github-actions
Copy link
Contributor

Missing required label for changelog. Requires at least 1 of: bug, developer, dependencies, internal, localization, major-bug, major-rfe, rfe, regression-fix, removed, skip-changelog. Found: .

You can add the required label by adding a comment with the following text: /label <category>

@Pankraz76
Copy link
Author

BUILD SUCCESS

Kindly request some feedback. Thanks.

fullName = i.getFullName();
}

private Object readResolve() {
Copy link
Contributor

@mawinter69 mawinter69 Aug 13, 2025

Choose a reason for hiding this comment

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

Do not remove any method with name readResolve or writeReplace
These methods even when private are used by during serialization of Objects.

Copy link
Author

Choose a reason for hiding this comment

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

again out bug sorry. yes.

Copy link
Author

Choose a reason for hiding this comment

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

public abstract static class Base<T> {
protected abstract void method();

private void aPrivateMethod() {}
Copy link
Contributor

Choose a reason for hiding this comment

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

The test in line 78 explicitly expects this method.

Copy link
Author

@Pankraz76 Pankraz76 Aug 13, 2025

Choose a reason for hiding this comment

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

thx, will exclude then.

return true;
}

private Object writeReplace() {
Copy link
Author

Choose a reason for hiding this comment

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

openrewrite/rewrite-static-analysis@976d366

1to1 the same phrase:

private Object writeReplace

Choose a reason for hiding this comment

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

So there's a conditional that checks if the class implements serializable; that appears not to be the case here; I think we can just remove that condition and just never remove methods with any of those names.

Choose a reason for hiding this comment

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

Copy link
Author

@Pankraz76 Pankraz76 Aug 13, 2025

Choose a reason for hiding this comment

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

thanks once again, teamwork makes the dreamwork.

@Pankraz76
Copy link
Author

Pankraz76 commented Aug 13, 2025

reopen after 2.15.1 release.

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