|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Thanks for looking int this Alex,
Unfortunately I am still unable to reproduce this issue - and I have tried upgrading from many versions of the plugins at the same time as upgrading Jenkins to 1.504 accross all of cifs, ftp and ssh. I suspect that the problem is JVM version specific.
I'd like to identify exactly where the problem lies, and and only fix there (i.e I do not really want to pull the minimum required version of jenkins to a version that is even newer than the current LTC RC)
The issue could potentially be solved with a calculated serialVerUID - a readResolve method is not supposed to concern itself with any sub or supertypes (so another possible fix may be to return "this" from readResolve in the serialized class definition)
I will be able to dedicate a large amount of time to this issue following this weekend.
Can everyone with this problem please provide their os, version including architecture and the full details of the JVM that the jenkins master is using?