-
Notifications
You must be signed in to change notification settings - Fork 52
#200 [core] Migrate to Java 21
#201
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
Conversation
Migrate to Java 21Migrate to Java 21
|
will release |
|
You need also to adjust CI/CD pipeline |
apply remove this
is it located in this repo, please? where to find this? |
maven-verify.yaml |
|
you mean this? https://github.com/apache/maven-pmd-plugin/blob/master/.github/workflows/maven-verify.yml |
|
Yes this file. Documentation for our gha can be found here https://github.com/apache/maven-gh-actions-shared |
|
@slachiewicz Why are you entertaning this and wasting your time? I'd close it straight away. |
|
yes if not fully agreed upon nor approved efforts should be kept small before investing. |
|
@michael-o i don't think that helping contributors to explain how our ci/cd works is wasting my time. Every new energy is valuable to OSS community. Also vote to migrate to Maven 21 was open on user/dev mailing list. Also OSS recipes like https://docs.openrewrite.org/recipes/java/migrate/upgradetojava21 could see how much work is to migrate to Java 21. |
The waste of time is trying to migrate this plugin to 21. |
|
The version 3.x of plugin is dedicated to Maven 3.x which is JDK 8 .... so it will still be a JDK 8 First we need to migrate API to Maven 4.x |
slawekjaranowski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3.x should stay on JDK 8
#200 [core]
Migrate to Java 21Migrate to Java 21pmd/pmd#5714[INFO] BUILD SUCCESS