Skip to content

Conversation

@Pankraz76
Copy link

@Pankraz76 Pankraz76 commented Apr 30, 2025

#200 [core] Migrate to Java 21

[INFO] BUILD SUCCESS

@Pankraz76 Pankraz76 changed the title #5713 [core] Migrate to Java 21 #200 [core] Migrate to Java 21 Apr 30, 2025
@Pankraz76
Copy link
Author

Pankraz76 commented Apr 30, 2025

will release maven-pmd-plugin:4.0.0 - Migrate to Java 21 to be used in:

@slachiewicz
Copy link
Member

You need also to adjust CI/CD pipeline

apply remove this
@Pankraz76
Copy link
Author

Pankraz76 commented May 2, 2025

You need also to adjust CI/CD pipeline

is it located in this repo, please? where to find this?

@slachiewicz
Copy link
Member

You need also to adjust CI/CD pipeline

is it located in this repo, please? where to find this?

maven-verify.yaml

Pankraz76 added a commit to Pankraz76/maven-build-cache-extension that referenced this pull request May 3, 2025
@Pankraz76
Copy link
Author

you mean this? https://github.com/apache/maven-pmd-plugin/blob/master/.github/workflows/maven-verify.yml
I did not found any java version in this and googled: apache/maven-build-cache-extension#211
This looks more adjustable.

@slachiewicz
Copy link
Member

Yes this file. Documentation for our gha can be found here

https://github.com/apache/maven-gh-actions-shared

@michael-o
Copy link
Member

@slachiewicz Why are you entertaning this and wasting your time? I'd close it straight away.

@Pankraz76
Copy link
Author

yes if not fully agreed upon nor approved efforts should be kept small before investing.

@slachiewicz
Copy link
Member

@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.

@michael-o
Copy link
Member

@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.

@slawekjaranowski
Copy link
Member

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

Copy link
Member

@slawekjaranowski slawekjaranowski left a 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

@Pankraz76 Pankraz76 closed this May 11, 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.

4 participants