Hi Jesse, thanks for the feedback. I already had a short look into this. It must be related to the changed remoting, the exception appears in the log but is not carried as root cause of the caught IOException any more. I did not find a way to get the "cause" exception based on the references at hand. I also do not know if this changed behavior of remoting is by intention or the root cause of the issue.
Kind Regards, Andreas. Am Donnerstag, 2. Februar 2017 14:25:51 UTC+1 schrieb Jesse Glick: > > On Thu, Feb 2, 2017 at 5:09 AM, Andreas Mandel <andreas...@gmail.com > <javascript:>> wrote: > > The mechanism to switch the jdk used to run maven to the platform jdk if > a > > "UnsupportedClassVersionError" is caught does not kick in because this > > exception is not carried as cause any more and thus this situation is > not > > detected. > > Well the simplest way forward is to fix that so we can use the > existing workaround for a while longer. Figure out where the initial > error is not thrown, where it is caught, how it is thrown up. I have > no particular advice beyond running a debugger and/or adding some > `println`s. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d6ba23e4-09a6-41c7-9de5-4c10bf3cd3bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
