gstanchev

Additionally, if i pull "master" from this project and "mvn clean package", it fails to compile with ``` [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /D:/work/ITOM/playground/frontend-maven-plugin/frontend-plugin-core/src/main/java/com/github/eirslett/maven/plugins/frontend/lib/FileDownloader.java:[14,23] package org.apache.http...

Okay, so after building and installing 1.12.2-SNAPSHOT locally with added httpcore dependency, and pointing our project to use that, tests are no longer failing so I can confirm it fixes...

We have ran into this (or similar) issue as well so interested to see the outcome of the investigation. We have a table that has a column name value. Here...

BTW once the DB is created this way, everything is reproducible from the H2 console (select, update, etc)

Sorry but is anyone looking into this issue? Any workaround we can do? Any status update? @kataggart any info will be much appreciated!

The uppercase would not work for us since we have support for multiple databases but adding a changelog entry to rename the column from "value" to "additional_value" did the trick...

As a temporary workaround i have set -Dorg.bouncycastle.jsse.client.dh.unrestrictedGroups=true which allows the handshake to proceed but it is a bandaid solution

  [-163424329, 142542871, 1923267286, -1455230203, -386313455, 961525489, 1857637176, 551158183, 1453528297, -1891609101, -804796725, 1135187117, -145988474, 1240992899, -1117394665, -727592112, -118138529, -596225457, 1027444187, -828776105, -1839608323, -1196526513, -973310276, -2084223184, 1640922313, 1727993337, -1141010082, -956192045,...

I was able to step through and " DHGroup dhGroup = getStandardGroupForDHParameters(p, g);" returns -1 and then "if (!dhGroupVerifier.accept(dhGroup))" returns false due to DefaultTlsDHGroupVerifier.checkGroup(DHGroup dhGroup) returns false due to not...

I don't have a control over the SSLContext as the issue is on the bottom of a JDBC client making connection to a Postgres service - both running in a...