AdoptOpenJDK vendor not used/detected after install

[StevenJDH]

I recently started using the maven-enforcer-plugin to warn if AdoptOpenJDK as a Java vendor wasn't being used, which works locally, but after the first pipeline run, it detected a different vendor in use as you can see here:

1247  Warning:  Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVendor warned with message:
1248  Eclipse Foundation is not an included Required Java Vendor

The expectation is that this would not throw a warning because I use AdoptOpenJDK/install-jdk@v1.1.1 before this step with the following configuration:

- name: Install AdoptOpenJDK
  uses: AdoptOpenJDK/install-jdk@v1.1.1
  with:
    version: '16'
    architecture: x64
    impl: hotspot

Is something in the environment not being set by this action that causes Eclipse Foundation to be the detected vendor that my project is compiling against?

I will be testing soon to see if using actions/setup-java produces the same result as this action is now more configurable with import features like configuring the global settings.xml file for automated deployments to maven central, however, for regular build workflows, I still prefer to use AdoptOpenJDK/install-jdk.

[karianna]

AdoptOpenJDK has moved to the Eclipse Foundation as Eclipse Adoptium (which produces Eclipse Temurin binaries). I suspect that's why you're seeing Eclipse Foundation as a vendor now.

[StevenJDH]

Ah yes, I remember this announcement.

Assuming that is the cause, then why is it when I run mvn enforcer:display-info on a project using this plugin on my local machine with AdoptOpenJDK 16 installed it confirms the vendor as AdoptOpenJDK, but in the pipeline using the AdoptOpenJDK action for version 16 the vendor is Eclipse Foundation? Is the package used by the action coming from Eclipse or the AdoptOpenJDK website? My expectation is that they should be the same package.

[TheMrMilchmann]

Your configuration pulls the latest JDK 16 build (which is 16.0.2+7 at the time of writing). My guess is that your local installation is older than that and still uses the old vendor string. Updating to a recent release should solve this problem and should display Eclipse Foundation as vendor locally too.

[StevenJDH]

@TheMrMilchmann, yes, this has to be it. On my local system I am still running 16.0.1+9 so it is likely there is a recent change in the vendor string. I'll update later. Thanks for the help on this clarification. I've also updated my rule in the plugin to also account for this vendor change, so I am satisfied.