Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WFMP-182] Update WildFly runtime image names #287

Merged
merged 1 commit into from
Feb 14, 2023

Conversation

jmesnil
Copy link
Member

@jmesnil jmesnil commented Feb 14, 2023

Use the new naming convention for the WildFly runtime image. They all have the same name, quay.io/wildfly/wildfly-runtime and uses tags to specify the JDK version.

By default, jdkVersion is no longer set so that the WildFLy runtime image will use its latest tag by default. This tag corresponds to the most recent LTS JDK version provided by WildFly (11 at the moment, eventually 17, etc).

User can stay on a specify JDK version by setting to 11 or 17.

JIRA: https://issues.redhat.com/browse/WFMP-182

Signed-off-by: Jeff Mesnil jmesnil@redhat.com

@jmesnil jmesnil force-pushed the WFMP-182_update_wildfly_image_names branch 2 times, most recently from 008293c to dbd380a Compare February 14, 2023 19:27
Use the new naming convention for the WildFly runtime image.
They all have the same name, `quay.io/wildfly/wildfly-runtime` and uses tags
to specify the JDK version.

By default, `jdkVersion` is no longer set so that the WildFLy runtime
image will use its latest tag by default. This tag corresponds to the
most recent LTS JDK version provided by WildFly (11 at the moment,
eventually 17, etc).

User can stay on a specify JDK version by setting <jdk-version> to 11 or 17.

JIRA: https://issues.redhat.com/browse/WFMP-182

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>
@jmesnil jmesnil force-pushed the WFMP-182_update_wildfly_image_names branch from dbd380a to ba582fd Compare February 14, 2023 22:02
@jamezp jamezp merged commit 746d920 into wildfly:main Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants