Skip to content

Conversation

@dhasani23
Copy link
Contributor

Problem

Support transformations to Java 21.

Solution

Add support.


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dhasani23 dhasani23 requested review from a team as code owners January 22, 2025 20:45
@dhasani23
Copy link
Contributor Author

TO-DO: add changelog

message.tabID
)

if (fromJDKVersion === JDKVersion.JDK21 && toJDKVersion === JDKVersion.JDK17) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why block this but allow other downgrades? e.g. 21 -> 11

Copy link
Contributor Author

@dhasani23 dhasani23 Jan 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only this one is possible

The source Java versions we show in dropdown form are: 8, 11, 17, 21
The target Java versions we show in dropdown form are: 17, 21

So the only downgrade possible for user to select is 21 -> 17

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So in other words you don't allow downgrades. This is a confusing if statement if that is the original intent, can we maybe check that source version is not >= target version? Or a comment at the very least.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added comment

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added another comment to make it more specific but after that LGTM


export const AWSTemplateCaseInsensitiveKeyWords = ['cloudformation', 'cfn', 'template', 'description']

// TO-DO: make sure all Strings look good for Java 21
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you still working on this TODO or did we just want to keep it in?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strings should be good, will remove this comment when confirmed

'This diff patch covers the set of upgrades for Springboot, JUnit, and PowerMockito frameworks.',
'This diff patch covers the set of upgrades for Springboot, JUnit, and PowerMockito frameworks in Java 17.',
'Prepare minimal upgrade to Java 21':
'This diff patch covers the set of upgrades for Springboot, JUnit, and PowerMockito frameworks in Java 21.',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't looked at the closures for java 21 (I can look), but assuming they make the same corresponding upgrades as the first patch for java 17

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes will confirm, but that should be true

const sourceLanguageVersion = `JAVA_${transformByQState.getSourceJDKVersion()}`
const targetLanguageVersion = `JAVA_${transformByQState.getTargetJDKVersion()}`
// TO-DO: remove these logs statements
console.log('sourceLanguageVersion', sourceLanguageVersion)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming you'll be removing these

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops I just saw the GitHub comments my bad!

@dhasani23 dhasani23 marked this pull request as draft January 24, 2025 23:09
@dhasani23
Copy link
Contributor Author

Need to receive confirmation that backend is ready for Java 21, so converting this PR to draft so that it is not accidentally merged, but it is ready.

@dhasani23
Copy link
Contributor Author

dhasani23 commented Jan 28, 2025

Ready to merge for 2/13 release

@dhasani23 dhasani23 marked this pull request as ready for review February 7, 2025 18:03
@dhasani23
Copy link
Contributor Author

/runIntegrationTests

@dhasani23 dhasani23 merged commit fb26635 into aws:master Feb 7, 2025
30 of 32 checks passed
s7ab059789 pushed a commit to s7ab059789/aws-toolkit-vscode that referenced this pull request Feb 19, 2025
## Problem

Support transformations to Java 21.

## Solution

Add support.

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: David Hasani <[email protected]>
Co-authored-by: Maxim Hayes <[email protected]>
@aws aws deleted a comment from github-actions bot Jun 25, 2025
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