Now that Java 16 is out, we really need to look at this IMO but I would
like help from the community.
My initial guess that this a JDK bug might be wrong and it could be an
issue in our code.
Gary
On Tue, Feb 23, 2021, 22:13 Gary Gregory wrote:
> Hi All:
>
> If you feel so inclined, I'd like h
Thank you for the explainer Ralph :-)
Gary
On Sat, Mar 20, 2021, 13:27 Ralph Goers wrote:
> We just concluded this same discussion for Log4j. I looked at the JRebel
> 2021 report [1] to gauge the number of people using a particular Java
> version. Respondents were able to select multiple versio
We just concluded this same discussion for Log4j. I looked at the JRebel 2021
report [1] to gauge the number of people using a particular Java version.
Respondents were able to select multiple versions so the numbers don’t add up
to 100%.
Java 7 or older.15%
Java 8 69%
Java
They choose to update not, no one forces updates magically, unless you
always pick up the latest by not specifying a version in a POM (bad
practice).
If they are still on Java 6 or 7, then updating libraries might not be a
priority.
Gary
On Sat, Mar 20, 2021, 07:27 John Patrick wrote:
> Some c
Some customers might need to use Java 7, but what about the customers
who want to use it on Java 17 which will be in rampdown in 5 months
and released in 6 months?
Also from memory from conferences ~ 2018/2019 I thought Java 17 was
planning on removing the Classpath so everything needed to be Modul
