|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15466) Fatal Error No Cl... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... [email protected] (JIRA)

The patch I uploaded was written against 1.480.1 (the LTS branch /stable), not against the bleeding edge code, hence I wouldn't be surprised if it doesn't apply directly.
One would hope that this sort of bug would be fixed in the LTS build as well (as that's what I'm running, and I found this JIRA by googling against the error I was seeing!).
The patch itself is dead trivial and probably easier for someone with commit-rights to hand-craft the code instead of doing a patch - just surround the call to Kernel32Utils in a try/catch, catch NoClassDefFoundError and ignore it, allowing execution to continue on to the general case.
i.e. replace
return Kernel32Utils.isJunctionOrSymlink(file);with