(maven) 01/01: Re-include macOS JLine native libraries in distribution (fixes #12759)

[gn...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

gnodet pushed a commit to branch fix/12759
in repository https://gitbox.apache.org/repos/asf/maven.git

commit 05705acea06c2d8a6ae5398cef1b8725e3db2ded
Author: Guillaume Nodet <gn...@gmail.com>
AuthorDate: Thu Aug 27 21:07:05 2026 +0200

    Re-include macOS JLine native libraries in distribution (fixes #12759)
    
    JLine 4.4.0 now ships macOS native binaries signed with an Apple
    Developer ID certificate and hardened runtime (jline/jline3#2173),
    so Gatekeeper will accept them even when the quarantine flag is set.
    
    This reverts the exclusion added in #10747 (commit f81a828777) which
    removed the Mac binaries to work around unsigned-binary Gatekeeper
    warnings.  With signed binaries the workaround is no longer needed,
    and re-including them avoids the regression where JLine's JAR-fallback
    extraction creates a fresh temp file on every invocation — making it
    impossible for users to permanently clear the quarantine flag.
    
    Co-Authored-By: Claude Opus 4.6 <no...@anthropic.com>
---
 apache-maven/pom.xml | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/apache-maven/pom.xml b/apache-maven/pom.xml
index 13d809a7b4..0187eace7c 100644
--- a/apache-maven/pom.xml
+++ b/apache-maven/pom.xml
@@ -177,9 +177,6 @@ under the License.
             <configuration>
               <includeArtifactIds>jline-native</includeArtifactIds>
               <includes>org/jline/nativ/**</includes>
-              <!-- exclude Mac OS binaries to prevent them from being marked with quarantine flag (https://github.com/apache/maven/issues/10747) and therefore being protected via Gatekeeper
-                    see also https://www.cisa.gov/eviction-strategies-tool/info-attack/T1144 -->
-              <excludes>org/jline/nativ/Mac/**</excludes>
             </configuration>
           </execution>
         </executions>