On 04.04.2020 03:25, Eric Bresie wrote: > Are you behind a proxy? I had problems with another application which > required registering certificates and related credentials keys to be added > for java.
No, no proxy server (my setup has direct access). ---rony > On April 2, 2020 at 2:20:44 PM CDT, Johan Vos <johan....@gluonhq.com> wrote: > I have no scientific evidence for this, but I remember issues related to > SSL with some JDK's as well, which may or may not be related to the cacerts > file that is bundled. > > - Johan > > On Thu, Apr 2, 2020 at 6:52 PM Rony G. Flatscher <rony.flatsc...@wu.ac.at> > wrote: > >>> Being stuck (tried the previous working gradle 5.6.4, could get "gradle >>> clean", but not further) in >>> the end I just tried Java 14 and that allowed me to run "gradle" >>> successfully (currently building >>> webkit to get going again). Just wanted to let interested readers know. >>> (Would be great though, if >>> it worked with the 11 LTS version as well.) >>> >>> ---rony >>> >>> >>> On 31.03.2020 20:36, Rony G. Flatscher wrote: >>>> On 31.03.2020 20:21, Scott Palmer wrote: >>>>>> Could not resolve all dependencies for configuration ':apps:lucene'. >>>>>> Multiple build operations failed. >>>>> java.lang.ExceptionInInitializerError >>>>> java.lang.NoClassDefFoundError: Could not initialize class >>>>> sun.security.ssl.SSLContextImpl$TLSContext >>>>> java.lang.NoClassDefFoundError: Could not initialize class >>>>> sun.security.ssl.SSLContextImpl$TLSContext >>>>>> java.lang.ExceptionInInitializerError >>>>>> java.lang.NoClassDefFoundError: Could not initialize class >>>>> sun.security.ssl.SSLContextImpl$TLSContext >>>>>> java.lang.NoClassDefFoundError: Could not initialize class >>>>> sun.security.ssl.SSLContextImpl$TLSContext >>>>> >>>>> >>>>> This to me looks like it may be failing to make an https connection to >>> a repository when >>>>> attempting to download dependencies. >>>>> >>>>> There are reports of NoClassDefFoundError w.r.t. SSLContextImpl when >>> running gradle builds, see: >>>>> https://github.com/gradle/gradle/issues/7842 >>>>> >>>>> Claims to be fixed, but maybe not? >>>>> >>>>> If it is related to Gradle changing java.home while compiling, I wonder >>> if using --no-parallel >>>>> might work around it? Of course try with --debug as well to see if it >>> offers more clues. >>>> Scott, thank you! >>>> >>>> Not having any knowledge about gradle I am unfortunately lost in this >>> case. However, I used "gradle >>>> --no-parallel --debug" which did not succeed but created a 1.2 MB text >>> file which I keep temporarily >>>> in my DrobBox at: < >>> https://www.dropbox.com/sh/e7seg9kgnm4wn4j/AAB4H4beZd9cJKbpvjyxdNMBa?dl=0 >>>> . >>>> >>>> Will have to leave in a few minutes for today so can only try other >>> things tomorrow. >>>> ---rony
