[
https://issues.apache.org/jira/browse/MNG-8471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916071#comment-17916071
]
Tamas Cservenak edited comment on MNG-8471 at 1/22/25 2:48 PM:
---------------------------------------------------------------
First, as [~gnodet] said, all this were happening in Maven 3 as well (different
native "C lib" but same thing).
Am fine that "Apple is correct here", but again, no OSS developer/project will
shell out $$$ to make it "not happen" to end users on Macs. Just like on ANY
OSS website has written, when you download anything, you MUST to verify that
same thing (usually with shasum or gpg signature). What instead, if Mac user
who knows what he's doing handles this as well (as I do hope that downloaded
distro WAS verified after browser download)? After all, it is he, who
downloaded the thing in the first place. You are true about HTTP/HTTPS, but
again, to make that happen, we did code change and we did not had to pay to
anyone to make it happen. So how can you pull in that as parallel to this issue
here?
was (Author: cstamas):
First, as [~gnodet] said, all this were happening in Maven 3 as well (different
native "C lib" but same thing).
Am fine that "Apple is correct here", but again, no OSS developer/project will
shell out $$$ to make it "not happen" to end users on Macs. Just like on ANY
OSS website is written, when you download anything, you need to verify that
same thing (with shasum or gpg signature). What instead, if Mac user who knows
what he's doing handles this as well (as I do hope that downloaded distro WAS
verified after browser download)? After all, it is he, who downloaded the thing
in the first place. You are true about HTTP/HTTPS, but again, to make that
happen, we did code change and we did not had to pay to anyone to make it
happen. So how can you pull in that as parallel to this issue here?
> library load disallowed by system policy on Mac
> ------------------------------------------------
>
> Key: MNG-8471
> URL: https://issues.apache.org/jira/browse/MNG-8471
> Project: Maven
> Issue Type: Bug
> Affects Versions: 4.0.0-rc-2
> Reporter: Elliotte Rusty Harold
> Priority: Blocker
> Attachments: Screenshot 2024-12-25 at 6.10.01 PM.png
>
>
> On a Mac with Sequoia 15.1.1 running the binary 4.0-RC2 release to "mvn clean
> verify" the maven-compiler-plugin
> {code}
> WARNING: Failed to load native library:libjlinenative.jnilib. osinfo:
> Mac/arm64 (caused by: java.lang.UnsatisfiedLinkError:
> /opt/java/apache-maven-4.0.0-rc-2/lib/jline-native/Mac/arm64/libjlinenative.jnilib:
>
> dlopen(/opt/java/apache-maven-4.0.0-rc-2/lib/jline-native/Mac/arm64/libjlinenative.jnilib,
> 0x0001): tried:
> '/opt/java/apache-maven-4.0.0-rc-2/lib/jline-native/Mac/arm64/libjlinenative.jnilib'
> (code signature in <E83722FF-713D-3654-A603-EEBC715887FE>
> '/opt/java/apache-maven-4.0.0-rc-2/lib/jline-native/Mac/arm64/libjlinenative.jnilib'
> not valid for use in process: library load disallowed by system policy),
> '/System/Volumes/Preboot/Cryptexes/OS/opt/java/apache-maven-4.0.0-rc-2/lib/jline-native/Mac/arm64/libjlinenative.jnilib'
> (no such file),
> '/opt/java/apache-maven-4.0.0-rc-2/lib/jline-native/Mac/arm64/libjlinenative.jnilib'
> (code signature in <E83722FF-713D-3654-A603-EEBC715887FE>
> '/opt/java/apache-maven-4.0.0-rc-2/lib/jline-native/Mac/arm64/libjlinenative.jnilib'
> not valid for use in process: library load disallowed by system policy),
> enable debug logging for stacktrace)
> {code}
> The build still seems to complete normally.
> openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Further, this isn't just a warning on the console. The mac actually pops up
> two alert dialogs to warn about this problem that user must click away during
> the build.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
