[JENKINS-69868] Avoid deserialization of anonymous classes - #61
[JENKINS-69868] Avoid deserialization of anonymous classes#61chriskloe wants to merge 12 commits into
Conversation
Avoid deserialization of anonymous classes. Found a hint in the console log and followed the advice: https://www.jenkins.io/doc/developer/extensibility/serialization-of-anonymous-classes/
Let eclipse generate some missing serialVersionUIDs
gounthar
left a comment
There was a problem hiding this comment.
Looks good to me.
Thanks.
|
The failure is due to a network or machine connection problem, not to the code itself. |
|
Thanks for the contribution @chriskloe . Apologies that it took so long to merge. |
|
No need to apologize, there has not been a release for some time. Even my first fix is not released yet. On my server I'm working with a locally built version. Maybe enabling incremental builds will help here. |
|
@chriskloe the CVS plugin could really use a new maintainer. Are you still using the plugin? If so, are you interested in adopting the plugin? Active users of a plugin are often the best maintainers, since they are most likely to release new versions as needed and are most likely to merge pull requests and verify them. |
Avoid deserialization of anonymous classes. Found a hint in the console log and followed the advice: https://www.jenkins.io/doc/developer/extensibility/serialization-of-anonymous-classes/
Affected issue: JENKINS-69868