[
https://issues.apache.org/jira/browse/MENFORCER-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170233#comment-17170233
]
Matt Nelson commented on MENFORCER-338:
---------------------------------------
Thought of another reason why a list of includes would be helpful. The recent
announcement of Eclipse taking over AdoptOpenJDK is going to result in a change
of the vendor name. During this transition period I imagine there will some
overlap where both vendors would be acceptable.
https://github.com/AdoptOpenJDK/TSC/issues/160#issuecomment-646807353
{code:xml}
<requireJavaVendor>
<includes>
<include>AdoptOpenJDK</include>
<include>Eclipse Adoptium</include>
</include>
</requireJavaVendor>
{code}
> Along with JavaVersion, allow enforcement of the JavaVendor
> -----------------------------------------------------------
>
> Key: MENFORCER-338
> URL: https://issues.apache.org/jira/browse/MENFORCER-338
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Reporter: Jeffrey Bennett
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.0.0-M4
>
>
> It would be useful to be able to ensure that a particular vendor JDK is being
> used. For example, I may need to confirm that we are using AdoptOpenJDK
> 1.8.0_232 and not Oracle JDK 1.8.0_232.
>
> I would assume that you would define a set of enums for the vendors - e.g.
> (OracleJDK, AdoptOpenJDK, JavaOpenJDK, and maybe a few others) so that it
> would look something like this to insure that either Adopt or Amazon JDK
> vendor was used.
> EDIT: implemented as below, to be in line with RequireOs
> {code:xml}
> <requireJavaVendor>
> <name>Oracle Corporation</name>
> </requireJavaVendor>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
