You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 withupstream/main
.We should try to fill in the voids (some
TODO
in the code), cherry-picking code whenever it's possible from theadd-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.The text was updated successfully, but these errors were encountered: