Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Classgraph can't find percent-encoded Coursier paths for private repositories
See original GitHub issueI’m using classgraph to resolve artifacts in sbt project with coursier.
We have two dependency types:
- Pusblished on public repositories
- Published on our private repository
While running under JDK 10 (OpenJDK 64-Bit Server VM Zulu10.3+5 (build 10.0.2+13, mixed mode)) within SBT or under Idea classgraph fails to resolve any classes from private repo artifacts.
At the same time it resolves these classes without an issue in case I gather all the dependencies manually into a directory and run java providing them all as classpath entries.
I’m almost sure that this is happening because of crappy directory naming convention used by coursier:
/Users/<user>/Library/Caches/Coursier/v1/https/<username>%40<company>.com%40<company>.jfrog.io/<company>/<repo>/com/<company>/<artifact>/<version>/<name>.jar
Seems like classgraphs fails to scan directories with % in name.
All such jars are completely missing from classgraph debug output.
Issue Analytics
- State:
- Created 5 years ago
- Comments:19 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ll report back in case of any issues.
Strange – there may have been a change in URL or file path handling in JDK 10 that causes this issue.
Either way, ClassGraph 4.6.0 (which implements the new behavior, and should be released soon) should not exhibit a regression, if the classpath is set up as typical (without “file:” or “jar:file:” prefixes on classpath entries).