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
On 02.04.2020 21:20, Johan Vos 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.
When hitting this problem the JDK was the same that has worked flawlessly with
th
Are you behind a proxy? I had problems with another application which required
registering certificates and related credentials keys to be added for java.
Eric Bresie
ebre...@gmail.com
> On April 2, 2020 at 2:20:44 PM CDT, Johan Vos wrote:
> I have no scientific evidence for this, but I remember
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
wrote:
> Being stuck (tried the previous working gradle 5.6.4, coul
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
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
> 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.la
On 31.03.2020 19:10, Kevin Rushforth wrote:
> That's not the problem. The minimum build number only applies if at the exact
> minimum JDK version
> in question. You are using 11.0.6 which is > 11 so no problem there.
>
> One last thing to try:
>
> $ rm -rf .gradle buildSrc/.gradle buildSrc/build
>
That's not the problem. The minimum build number only applies if at the
exact minimum JDK version in question. You are using 11.0.6 which is >
11 so no problem there.
One last thing to try:
$ rm -rf .gradle buildSrc/.gradle buildSrc/build
In case something is cached there that the newer gradl
Hmm, noticed a JDK "minimum jdk build number: 28" minimum build number.
Currently using the latest
AdoptOpenJDK 11 LTS.
If that is the problem which JDK would you suggest to use instead?
---rony
On 31.03.2020 18:51, Rony G. Flatscher wrote:
> On 31.03.2020 18:20, Kevin Rushforth wrote:
>> Che
On 31.03.2020 18:20, Kevin Rushforth wrote:
> Check your JDK version and gradle version:
>
> $ java -version
> $ gradle -version
>
> If they look OK, you might try:
>
> $ rm -rf build
> $ gradle clean
>
> and then do a build.
Thank you, Kevin, unfortunately, it does not work out (it fails at "grad
Check your JDK version and gradle version:
$ java -version
$ gradle -version
If they look OK, you might try:
$ rm -rf build
$ gradle clean
and then do a build.
-- Kevin
On 3/31/2020 8:06 AM, Rony G. Flatscher wrote:
After merging the master into a local branch, gradle fails with two except
After merging the master into a local branch, gradle fails with two exceptions.
After updating to
6.3 it still fails, here the output:
rony@rony-linux:~/dev/github/openjdk/jfx$ gradle --stop
Stopping Daemon(s)
1 Daemon stopped
rony@rony-linux:~/dev/github/openjdk/jfx$ gradle
13 matches
Mail list logo
