I've sent pull #8 [1], as IMHO it's better to use Lock instead of locking whole class. As mentioned in pull request, I'm no sure if it wouldn't be cheaper just catch the LinkageException, though. Vojta
[1] https://github.com/jenkinsci/remoting/pull/8 On Monday 05 November 2012 08:58:21 Stephen Connolly wrote: > I don't have enough confidence in that code, I would suggest that you fork > the repo in github, apply the patch and submit a pull request. Ping Kohsuke > (or perhaps Jesse) once you have the pull request, as they would be the > people I would ask to review any changes I had in that specific area of the > code-base. > > Pull requests are usually quickest to get applied. > > HTH > > -Stephen > > On 5 November 2012 08:01, Erik Løvlie <[email protected]> wrote: > > Hi all, can someone with commit rights please have a look at > > > > https://issues.jenkins-ci.org/browse/JENKINS-6604 > > https://issues.jenkins-ci.org/browse/JENKINS-15716 > > > > Myself and others have tried to communicate via jira, but with zero > > response. Someone has already taken the time to analyze the former issue > > and provide a patch, so assuming the problem has been identified we only > > need a maintainer to step up and commit the fix. Or at the very least > > provide some feedback. > > > > Brgds, > > Erik Lovlie
