[
https://issues.apache.org/jira/browse/MNG-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939366#comment-17939366
]
Lenny Primak edited comment on MNG-8399 at 3/29/25 2:55 AM:
------------------------------------------------------------
This issue also appears in Maven 4-rc-3.
I believe latest Guava has the fix, so it's a matter of upgrading Guava.
For maven 4, jansi is no longer an issue.
was (Author: lprimak):
This issue also appears in Maven 4-rc-3.
I believe latest Guava has the fix, so it's a matter of upgrading Guava
> JDK 24+ issues warning about usage of sun.misc.Unsafe
> -----------------------------------------------------
>
> Key: MNG-8399
> URL: https://issues.apache.org/jira/browse/MNG-8399
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.9.9
> Reporter: Marc Philipp
> Priority: Minor
> Attachments: build.log
>
>
> When running a build with JDK 24-ea+26 or later, the following warning is
> issued by default:
> {noformat}
> WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
> WARNING: sun.misc.Unsafe::objectFieldOffset has been called by
> com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper
> (file:/home/marc/.asdf/installs/maven/3.9.9/lib/guava-33.2.1-jre.jar)
> WARNING: Please consider reporting this to the maintainers of class
> com.google.common.util.concurrent.AbstractFuture$UnsafeAtomicHelper
> WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future
> release {noformat}
> The source of this can be further investigated using the
> {{--sun-misc-unsafe-memory-access=debug}} JVM argument from [JEP
> 498|https://openjdk.org/jeps/498#Identifying-uses-of-the-memory-access-methods-in-sun-misc-Unsafe]
> (see attached log file).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
