Hi folks,
I probably missed most of the fun here (overworked) but IMHO it makes sense to
update both projects to JDK 8
A related question - someone volunteering as release manager? Having said that
I can lend a hand for the code changes :)
Thanks in advance
Siegfried Goeschl
> On 29.03.2021
Calling it technical debt is pretty useful, too, because just like
monetary debt, it can be useful to accumulate some in the short term
for productive reasons, but if you don't pay it off and manage it
properly, the interest payments begin to dominate expenses. Interest
on technical debt comes in t
WRT rant:
We call that "technical debt" and to move the needle on that developers are
(sometimes or always depending on you company) asked to explain the
"business value" for spending the time (IOW the money) to do so. At which
point said developers roll their eyes, pull their remaining hair out, o
> If they are still on Java 6 or 7, then updating libraries might not be a
> priority.
>
> Gary
I second that.
If an organization is still reluctant to upgrade at least to JDK 8, its rather
unlikely that the same organization is urgently requiring to update to any
latest commons release.
An
> 2018-11-29-F008-Back40.csv
I work for NASA (as a contractor). It seems that for Macs, NASA, and perhaps
all of the federal government, don't yet support anything past Java 8. I have
no idea why...
-r
Randy Strauss
Software Engr, SWS/UAM/UTM, NASA Ames Research Center
-
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
On Sat, 21 Nov 2020 at 17:13, Gary Gregory wrote:
>
> On Sat, Nov 21, 2020 at 11:46 AM sebb wrote:
>
> > Note that Java 7 and later are all on lndefinite Sustaining Support:
> >
> > https://www.oracle.com/java/technologies/java-se-support-roadmap.html
> >
> > This is presumably because there are
On Sat, Nov 21, 2020 at 11:46 AM sebb wrote:
> Note that Java 7 and later are all on lndefinite Sustaining Support:
>
> https://www.oracle.com/java/technologies/java-se-support-roadmap.html
>
> This is presumably because there are customers who need Java 7.
>
And those paying Oracle customers ar
Note that Java 7 and later are all on lndefinite Sustaining Support:
https://www.oracle.com/java/technologies/java-se-support-roadmap.html
This is presumably because there are customers who need Java 7.
On Sat, 21 Nov 2020 at 16:18, Gary Gregory wrote:
>
> I do not see a reason to maintain EXE
12 matches
Mail list logo
