On 5/1/25 06:21, Guillaume Nodet wrote:
> The only way is to add the --enable-native-access=ALL-UNNAMED option in the
> shell scripts afaik.  We've already added it in master.
> Note that this option is not available in older JDK which are still
> supported by Maven 3.9.

-XX:+IgnoreUnrecognizedVMOptions should allow setting that flag on older JDKs 
without a launch failure.

its not great since this will obfuscate typos etc but sometimes useful in 
situations like this,

best regards,

michael


>
> ------------------------
> Guillaume Nodet
>
>
>
> Le jeu. 1 mai 2025 à 05:19, Mark Derricutt <m...@talios.com> a écrit :
>
>> Tamás, Guillaume -
>>
>> I note when running 3.9.9 under Java 24, I see:
>>
>> WARNING: A restricted method in java.lang.System has been called
>> WARNING: java.lang.System::load has been called by
>> org.fusesource.jansi.internal.JansiLoader in an unnamed module
>> (file:/Users/amrk/.sdkman/candidates/maven/current/lib/jansi-2.4.1.jar)
>> WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for
>> callers in this module
>> WARNING: Restricted methods will be blocked in a future release unless
>> native access is enabled
>>
>> I also see that jansi:2.4.2 has been released (although not appearing in
>> the Changelog yet):
>>
>> org.fusesource.jansi:jansi:2.4.2                           29 Apr 2025 at
>> 18:27 (NZST)
>>
>> Although looking at
>> https://github.com/fusesource/jansi/compare/jansi-2.4.1...jansi-2.4.2 it
>> doesn’t look like anything here will help with this.
>>
>> Not sure if there’s a ticket already for this (I may have raised one awhile
>> ago?) - is there any quick win/fix to hide/remove those warnings we could
>> get in a 3.9.10 release?
>>
>> Mark
>>
>> --
>> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
>> Porcupine Tree
>>
>>
>> On 28 Apr 2025 at 11:58:34 PM, Tamás Cservenák <ta...@cservenak.net>
>> wrote:
>>
>>> Howdy,
>>>
>>> quickly scanned some recent MNG JIRAs, and I think these would be good
>>> candidates as well:
>>>
>>> - https://issues.apache.org/jira/browse/MNG-8685 (limited mode, maybe
>>> only GHA along the lines of original PR?)
>>> - https://issues.apache.org/jira/browse/MNG-8663 (ASM update, it might
>>> happen already in 3.9.x) - but along with the sisu and guice switch to
>>> asm-less (non shaded) versions
>>> - https://issues.apache.org/jira/browse/MNG-8623 -- this is more
>>> "infra", make ITs use Mimir for caching just like master
>>> - https://issues.apache.org/jira/browse/MNG-8638 -- not backporting,
>>> but warning only? Also, IMO warning ONLY if values left uninterpolated
>>>
>>> will report with more
>>>
>>> On Fri, Apr 25, 2025 at 10:56 AM Tamás Cservenák <ta...@cservenak.net>
>>> wrote:
>>>
>>>
>>> Hej,
>>>
>>>
>>> Will take a peek and I think there is more to (both resolver and mvn3) it
>>> next week
>>>
>>>
>>> T
>>>
>>>
>>> On Thu, Apr 24, 2025, 23:31 Slawomir Jaranowski <s.jaranow...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>> I would like to release Maven 3.9.10
>>>> We have planned issues:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.10
>>>> I also would like to release resolver 1.9.23
>>>> with issues:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.23
>>>> I will work on it, I hope the release can be done in the next two -
>>> three weeks.
>>>
>>>> Any help as usual is appreciated.
>>>> --
>>>> Sławomir Jaranowski
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to