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
If I create a context from a maven project and for whatever reason (on purpose, on accident, ...) there is no byte-code available then source-code analysis only works for the root source location of the project (e.g. src/main/java). However, we should also try to read the sources from dependencies (source JARs or even module sources).
The text was updated successfully, but these errors were encountered:
Same issues as with #5 also applies here: We would need to resolve sources of all dependencies transitively. The nice thing about the ClassLoader is that it already solves many issues for us and via ProtectionDomain and CodeSource we can determine the location for lazy initiailization. This all can not be used if the byte-code can not be found via ClassLoader.
If I create a context from a maven project and for whatever reason (on purpose, on accident, ...) there is no byte-code available then source-code analysis only works for the root source location of the project (e.g.
src/main/java
). However, we should also try to read the sources from dependencies (source JARs or even module sources).The text was updated successfully, but these errors were encountered: