Hi all,
Regarding the issue I mentioned, I found that using
`@SuppressStaticInitializationFor("<fullname-of-your-class>")` might be a
solution. The problem I encountered has been resolved using this approach, but
I'm not entirely sure if it's universally applicable. If you're facing similar
issues, you might want to give it a try.
BR,
Guangrong
Original
From: Fu Guangrong <[email protected]>
To: [email protected] <[email protected]>;[email protected]
<[email protected]>;
Cc: [email protected] <[email protected]>;
Date: 2023年08月24日 17:31
Subject: Re: [onap-discuss] [onap] Java 17 upgrade plans
Hi all,
I'm facing a problem with PowerMock while trying to upgrade Holmes to be Java
17 based. While using PowerMock.mockStatic, it gave me an "IllegalState Unable
to load cache item" error.
Anyone has an idea about this?
BR,
Guangrong
From: AmyZwarico <[email protected]>
To: [email protected] <[email protected]>;[email protected]
<[email protected]>;
Date: 2023年07月25日 08:46
Subject: Re: [onap-discuss] [onap] Java 17 upgrade plans
Thanks for the suggestion.
We discussed it on the 7/24 PTL call and decided to proceed with Java 17 to
avoid issues with dependencies not yet supporting Java 21 and to give Java 21
time to address any issues that arise. However, individual projects are welcome
to go straight to Java 21. It’ll be great to have a few projects with Java 21
experience so they can help the others.
Best regards,
Amy
From: [email protected] <[email protected]>
Sent: Friday, July 21, 2023 9:31 AM
To: [email protected]; ZWARICO, AMY <[email protected]>
Subject: Re: [onap] Java 17 upgrade plans
Hello,
Maybe as, since you have these goals to move to Java 17.
Why not skip 17 and go straight to Java 21 (LTS)?
https://en.wikipedia.org/wiki/Java_version_history
Java 21 will be release 19th September 2023 (so basically after the summer
vacations) of us all.
And the jump from 17 to 21 isn't that hard, so the ambition goal might be to
aim directly at 21 LTS instead of 17.
Especially since the ONAP roadmap is targeted for 2024.
Just a proposal, best regards, many greetings and a nice weekend.
Florian Bachmann
--------------------------------------------------------------------------------
From: [email protected] <[email protected]> on behalf of
Amy Zwarico <[email protected]>
Sent: Friday, July 21, 2023 14:45
To: [email protected] <[email protected]>
Subject: [onap-discuss] [onap] Java 17 upgrade plans
To prepare for Java SE 11 end of service life (EOSL), ONAP is encouraging
projects to develop a plan to upgrade from Java 11 to Java 17 by the end of 2024
2023: Java 17 is a Best Practice – new containers will use Java 17
2024: Java 17 is a Global Requirement for all ONAP containers
August 2024 – Java 17 migration complete for containers using Red Hat
December 2024 – Java 17 migration complete for all other Oracle and Azul
Java SE 11 EOSL dates: September 2026 for Oracle, September 2026 for Azul,
October 2024 for Red Hat
Jiras for Java 17 migration will be created for each affected project.
CCSDK, Policy, CPS have already migrated to Java 17 and are willing to share
their experiences with the other projects.
Best regards,
Amy Zwarico, Director - Cybersecurity
Chief Security Office / Network Security
AT&T Services
(205) 613-1667
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#24528): https://lists.onap.org/g/onap-discuss/message/24528
Mute This Topic: https://lists.onap.org/mt/100275827/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
