You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2024/07/11 10:55:00 UTC
[jira] [Updated] (MNG-8142) If JDK profile activator gets "invalid" JDK version for whatever reason, it chokes but does not tell why
[ https://issues.apache.org/jira/browse/MNG-8142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak updated MNG-8142:
---------------------------------
Fix Version/s: 4.0.0-beta-4
> 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: 4.0.0, 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)