[ 
https://issues.apache.org/jira/browse/MNG-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911256#comment-17911256
 ] 

Guillaume Nodet commented on MNG-8455:
--------------------------------------

Not calling guava is not doable.
As [~cstamas] commented in MNG-8505, 
{quote}
Maven 3 uses Eclipse Sisu/Plexus that uses Guice that uses Guava. Maven itself 
is not directly using Guava.
Maven 4 introduces Maven DI (native DI container) but Maven 4 has requirement 
to support Maven 3 stuff, hence it have to support legacy still, like Plexus DI 
is.
{quote}

We need to continue moving from Sisu/Plexus to DI and the new API in 
maven-core, which will help minimising the usage of Sisu/Plexus.

Closing this one as won't fix as suggested by [~elharo], as I don't see any 
easy fix to fix the problem, but to get rid of Maven 3 compatibility (which is 
more a plan for Maven 5) or to upgrade to a guava version which will fix the 
problem.

> WARNING deprecated method in sun.misc.Unsafe has been called
> ------------------------------------------------------------
>
>                 Key: MNG-8455
>                 URL: https://issues.apache.org/jira/browse/MNG-8455
>             Project: Maven
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 4.0.0-rc-2
>         Environment: $> mvn --version
> Apache Maven 4.0.0-rc-2 (273314404f85ec3c089e295d8b4e0cb18c287cf5)
> Maven home: /Users/khm/tools/apache-maven-4.0.0-rc-2
> Java version: 24-ea, vendor: Oracle Corporation, runtime: 
> /Users/khm/.sdkman/candidates/java/24.ea.28-open
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "aarch64", family: "mac"
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>             Fix For: 4.0.0
>
>
> Currently running a build under JDK 24.ea.28 will emit the following WARNING:
> {code}
> $> mvn verify
> 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:/Users/khm/tools/maven/lib/guava-33.3.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
> [INFO] 
> {code}
> I also tested with the built from current master of Maven Core which is using 
> {{guava-33.4.0-jre.ja}} which emits the same WARNING. 
> Tracking on Github: 
> * https://github.com/google/guava/issues/6806
> * https://github.com/google/guava/pull/7555



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to