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

feature(maven): Apply a set of rules to help with JDK8 upgrade #20

Closed
gounthar opened this issue Sep 30, 2024 · 0 comments
Closed

feature(maven): Apply a set of rules to help with JDK8 upgrade #20

gounthar opened this issue Sep 30, 2024 · 0 comments

Comments

@gounthar
Copy link
Owner

gounthar commented Sep 30, 2024

Whenever we have to upgrade an outdated plugin, we face the problem a recent maven can't use JDK7, so we're stuck with a plugin we can't update.
I tried jenkins-infra#277 a few manual steps that helped me update a very outdated plugin, mostly by manipulating the existing pom.xml.

Could we use a pom parsing tool to remove offending properties, add parent pom, update Jenkins' minimal version, and so on?

We already made an attempt in #21, but the add-pom-modifier branch is not compatible anymore with upstream/main.

We should try to fill in the voids (some TODO in the code), cherry-picking code whenever it's possible from the add-pom-modifier branch in order to allow a plugin pom using a JDK version older than 8 to be transformed so we can apply standard recipes afterward.

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 a pull request may close this issue.

1 participant