On Thu, Feb 2, 2017 at 5:09 AM, Andreas Mandel <[email protected]> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0sVw0k5%2B4W7GBahBmx6E5oCt2biY%2B94szpDBRRy9Cg6A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
