[
https://issues.apache.org/jira/browse/MENFORCER-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653155#comment-17653155
]
Petr Široký commented on MENFORCER-445:
---------------------------------------
The error messages now look like this (unless there is a custom message
provided with the rule configuration):
{code:java}
[ERROR] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion failed
with message:
Detected JDK version 11.0.17
(JAVA_HOME=/usr/lib/jvm/java-11-openjdk-11.0.17.0.8-1.fc37.x86_64) is not in
the allowed range 17.
[ERROR] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVendor failed with
message:
Red Hat, Inc. is not an included Required Java Vendor
(JAVA_HOME=/usr/lib/jvm/java-11-openjdk-11.0.17.0.8-1.fc37.x86_64){code}
> Include Java Home in Message for Java Rule Failures
> ---------------------------------------------------
>
> Key: MENFORCER-445
> URL: https://issues.apache.org/jira/browse/MENFORCER-445
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Documentation, Standard Rules
> Affects Versions: 3.1.0
> Environment: Maven 3.8.5
> Reporter: Robert Krajewski
> Assignee: Slawomir Jaranowski
> Priority: Major
> Labels: enforcer, messages, up-for-grabs, usability
> Fix For: 3.2.0
>
>
> When Java rules fail, for example, when JDK version or vendor fails, knowing
> exactly which Java implementation caused the problem would be handy,
> especially when it happens in a CI system that might be setting up the Java
> to be used in a roundabout way. Including the Java home in the message should
> be enough.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
