-
Notifications
You must be signed in to change notification settings - Fork 15
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
Some plugins still using old versions of Java don't get detected as such #342
Comments
Maybe I'm mixing two things there...
I thought this was being handled by :
, but we may not even reach that recipe (see #307). 🤔 |
I think Must be done in a static way by implementing the TODOs (should not be too difficult) |
I'm working on it. 🤗 |
Jenkins and plugins versions report
The AnchorChain plugin for example is not declaring any
java.version
property that could help us identify we need a remediation.It is declaring a parent pom version, though:
The official documentation says:
Could we leverage that to treat the plugin as a pre-jdk8 plugin and remediate it?
What Operating System are you using (both controller, and any agents involved in the problem)?
WSL2/Debian
Reproduction steps
Expected Results
No error.
Actual Results
Anything else?
No response
Are you interested in contributing a fix?
Yes.
The text was updated successfully, but these errors were encountered: