-
-
Notifications
You must be signed in to change notification settings - Fork 357
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
chore(deps): update dependency org.kohsuke.metainf-services:metainf-services to v1.9 #4649
chore(deps): update dependency org.kohsuke.metainf-services:metainf-services to v1.9 #4649
Conversation
9801ac9
to
db82b1e
Compare
@monperrus there is a bug with depclean, and I added the dependency as ignored for depclean. But we can only ignore exact versions. For every new version of this dependency, we need to change it. Do you know the authors and can you report them the problem? |
ping @cesarsotovalero this CI failure seems to uncover a bug in depclean. Would you have a look at this? Thanks! |
Hi @MartinWitt, The dependency |
can we use a version wildcard in the ignoreDependencies tag, suc has |
Hi @monperrus,
This feature is not available at the moment. |
The bug is that we have to ignore the dependency. Normally, depclean should detect this dependency as used. Metainf-services is even present in the source code with its |
Hi @MartinWitt,
Where exactly is the |
Hi @MartinWitt, I've investigated this issue. The The DepClean analysis is based on the information in the compiled One way to fix this issue is implementing additional static source code analysis in DepClean to catch these types of usages, but this is computationally expensive, AFAIK. So far the simplest way is to exclude the dependency from the analysis. If you know another way to catch this usage, please open an Issue and PR in the DepClean repo. DepClean uses ASM for bytecode analysis, see related SO question: https://stackoverflow.com/questions/63465374/how-to-visit-annotation-inside-method-in-asm |
Thank you for your investigation. This really seems like a limitation you can't solve as a byte code analysis tool. You could add this special case to your documentation to help other projects with the same problem. |
This PR contains the following updates:
1.8
->1.9
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by WhiteSource Renovate. View repository job log here.