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

CloudFormation CLI support to generate Java11 resource definitions #347

Open
jmuham opened this issue Jan 12, 2021 · 1 comment
Open

CloudFormation CLI support to generate Java11 resource definitions #347

jmuham opened this issue Jan 12, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@jmuham
Copy link

jmuham commented Jan 12, 2021

I recently initialized a new CloudFormation resource using the Java Plugin, and noticed it auto-generated config/code for Java8.

Since Lambda recently added Java11 runtime support, are there any instructions on how to generate for java 11, or a migration guide?

I am hoping there aren't many changes needed, but want to confirm if there are any plans or already supported solutions for getting set up with Java 11.

@taasjord
Copy link

taasjord commented Aug 19, 2022

It's not so "recently" anymore, and Java 8 is basically past end-of-life (even though Corretto might not be), so developers most likely wouldn't want to use that old version.

I did try to build with java11, but I got an error trying to provision the resource in a stack:

HandlerWrapper has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0

Does this mean Cloudformation runtime only supports registry resource on Java8?

EDIT: finally figured it out. There is a generated, undocumented and hidden (why?) file .rpdk-config that specifies the runtime version and that supports java11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants