[ 
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MENFORCER-349:
-------------------------------------
    Fix Version/s: 3.0.0-M4

> include JavaVendor in display-info output
> -----------------------------------------
>
>                 Key: MENFORCER-349
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-349
>             Project: Maven Enforcer Plugin
>          Issue Type: Improvement
>          Components: Plugin
>    Affects Versions: 3.0.0-M3
>            Reporter: Mark Symons
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.0.0-M4
>
>
> Include JavaVendor in the output of the {{display-info}} goal.
> This addition would make it much easier to determine whether Oracle or 
> OpenJDK is being used (or which flavour of OpenJDK).  Currently:
> {noformat}
> [INFO] --- maven-enforcer-plugin:3.0.0-M3:display-info (default-cli) @ xxxxx 
> ---
>  [INFO] Maven Version: 3.6.3
>  [INFO] JDK Version: 1.8.0_232 normalized as: 1.8.0-232
>  [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 
> 3.10.0-693.21.1.el7.x86_64
> {noformat}
> The JDK here is Zulu OpenJDK...  but one would have  to do some research to 
> know for sure that it could not be Oracle (a no-no in my organisation) where 
> the latest version at time of writing happens to be 1.8.0-221.
> MENFORCER-338 requests that Javavendor be enforceable.  I have voted for that 
> enhancement but log this as something that might (hopefully) be easier to 
> implement in the short term.
> It would also provide the benefit of making it clearer whether one has a 
> problem that requires going to the effort of configuring enforcement.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to