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

Add limited support for bundled signatures of a later JDK version than currently executing #208

Closed
uschindler opened this issue Oct 2, 2022 · 1 comment
Assignees
Labels

Comments

@uschindler
Copy link
Member

As we do not yet support forking in the Maven/Gradle task and using Toolkits, it is not always possible to run checks against class files of a later version than the current Gradle/Maven runtime.

The code should in addition to #207 do the following:

  • print a warning that scanning class files of later version than current runtime may not find all issues
  • disable unknown signatures silently
@uschindler uschindler self-assigned this Oct 2, 2022
@uschindler uschindler added this to the 3.5 milestone Oct 2, 2022
@uschindler
Copy link
Member Author

uschindler commented Oct 2, 2022

Actually this makes no sense, because if you run with a newer verson, the JDK related bundled sigantures are never available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant