[
https://issues.apache.org/jira/browse/MENFORCER-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717139#comment-17717139
]
Slawomir Jaranowski commented on MENFORCER-478:
-----------------------------------------------
There are from logs:
{noformat}
[DEBUG] Detected Java Version: '1.8.0_362'
[DEBUG] Normalized Java Version: '1.8.0-362'
[DEBUG] Parsed Version: Major: 1 Minor: 8 Incremental: 0 Build: 362 Qualifier:
null
{noformat}
So I can use {{1.8.0-370}} as version, and I have:
{noformat}
[ERROR] Detected JDK version 1.8.0-362
(JAVA_HOME=/usr/local/Cellar/openjdk@8/1.8.0+362/libexec/openjdk.jdk/Contents/Home/jre)
is not in the allowed range [1.8.0-370,).
{noformat}
I my case: {{1.8.0-362}} pass.
Similar when I use: {{{}17.0.99{}}}, I have
{noformat}
[ERROR] Detected JDK version 17.0.7
(JAVA_HOME=/usr/local/Cellar/openjdk@17/17.0.7/libexec/openjdk.jdk/Contents/Home)
is not in the allowed range [17.0.99,).
{noformat}
> Investigate if is it possible to exclude obviously obsolete versions
> --------------------------------------------------------------------
>
> Key: MENFORCER-478
> URL: https://issues.apache.org/jira/browse/MENFORCER-478
> Project: Maven Enforcer Plugin
> Issue Type: Task
> Components: requireJavaVersion
> Reporter: Tamas Cservenak
> Priority: Major
>
> Investigate is it possible to exclude obviously obsolete versions of Java.
> For example: When someone says "builds on Java 8", the obviously obsolete
> releases like Java 8u6 should be still banned.
> Natutally, strings changed between Java versions, so when someone says "Java
> 17" (current version is 17.0.7), we may want to exclude 17.0.1 or so?
> [https://www.oracle.com/java/technologies/javase/8all-relnotes.html]
> https://www.oracle.com/java/technologies/javase/17all-relnotes.html
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
