[MNG-8142] If JDK profile activator gets "invalid" JDK version for whatever reason, it chokes but does not tell why

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.9.8, 4.0.0-beta-4, 4.0.0
• Component/s: Core
• Assignee: Tamas Cservenak
• Reporter: Tamas Cservenak
• Created: 05/Jun/24 12:23
• Updated: 11/Jul/24 10:54
• Resolved: 06/Jun/24 16:52

Description

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.

Issue Links

• links to: GitHub Pull Request #1557