[
https://issues.apache.org/jira/browse/MNG-8505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911242#comment-17911242
]
Tamas Cservenak commented on MNG-8505:
--------------------------------------
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.
> WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
> --------------------------------------------------------------------------
>
> Key: MNG-8505
> URL: https://issues.apache.org/jira/browse/MNG-8505
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
> Affects Versions: 4.0.0-rc-2
> Environment: MacOS 15.3, M3 Max processor
> Reporter: Keith E Campbell
> Priority: Minor
>
> 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:/Library/Java/apache-maven-4.0.0-rc-2/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] Cache configuration is not available at configured path
> /Users/kec/IKE/ikm-framework-kec/.mvn/maven-build-cache-config.xml, cache is
> enabled with defaults
> [INFO] Using XX hash algorithm for cache
> [
>
> Do you really need to use Guava? I expect you are going to get quite a few of
> these issues, and if you can depend more on projects that are committed to
> complete JPMS support, it might be an easier path.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
