[
https://issues.apache.org/jira/browse/MNG-8142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852436#comment-17852436
]
ASF GitHub Bot commented on MNG-8142:
-------------------------------------
cstamas commented on PR #1557:
URL: https://github.com/apache/maven/pull/1557#issuecomment-2149772564
If this PR gets merged, the #1555 will become fixed as well, as there will
be no more ERRORs, as NumberformatEx is reported here as model builder warnings
with proper message.
The fact that these warnings are nowhere reported is totally different
thing, and probably a good cause for yet another PR, but it is out of scope of
3.9.8
> If JDK profile activator gets "invalid" JDK version for whatever reason, it
> chokes but does not tell why
> --------------------------------------------------------------------------------------------------------
>
> Key: MNG-8142
> URL: https://issues.apache.org/jira/browse/MNG-8142
> Project: Maven
> Issue Type: Bug
> Components: Core
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 3.9.8, 4.0.0-beta-4
>
>
> The JDK profile activator uses property {{java.version}} to determine is
> profile active or not, but if you look at MNG-3746 you can see that Maven
> _allows overriding that property_ by user, but also, today some "weird
> formatted" version may pop up in the wild.
> The JDK profile activator is not prepared for these cases, and will just
> throw (NumberFormatEx), without telling why it did belly up.
> Improve the message why it throw.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
