Maintenance: Remove Java 8 support in examples for v2 #1466
Assignees
Labels
good first issue
Good for newcomers
maintenance
priority:3
Neutral - not a core feature or affects less than 40% of users
status/staged-major-release
This change will go with the next major release
v2
Version 2
Milestone
Comments
scottgerring
added
good first issue
2 tasks
jeromevdl
changed the title
6 tasks
6 tasks
scottgerring
pushed a commit
that referenced
this issue
Dec 1, 2023
* Remove Java 8 issue #1466 * reverting pom to java 8 as change should only apply to examples * updated workflow to not build examples in java 8 workflow * updated syntax of workflow * excluding examples from spotbugs check for java 8 build * updated github actions workflow * updated workflows to have a comma seperated list of examples modules when java 8 to exclude * updating build syntax for non java 8 * updating gradle config for Java 11+ * updating the java version on spotbugs to 11
scottgerring
added
the
status/staged-major-release
|
This will be released in v2 |
scottgerring
moved this from Backlog
to Coming soon
in Powertools for AWS Lambda (Java)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Maintaining examples for both Java 8 and Java 11+ is a significant time sink, particularly in terms of weaving configuration.
We should use v2 as an opportunity to remove support from the examples for Java 8, implicitly steering our users towards newer, more efficient Java runtimes.
Why is this needed?
Which area does this relate to?
Other
Solution
No response
Acknowledgment
The text was updated successfully, but these errors were encountered: