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

ability to support source-code only projects #6

Open
hohwille opened this issue May 15, 2019 · 1 comment
Open

ability to support source-code only projects #6

hohwille opened this issue May 15, 2019 · 1 comment

Comments

@hohwille
Copy link
Member

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).

@hohwille
Copy link
Member Author

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.

hohwille added a commit that referenced this issue Oct 14, 2019
prevent close() from throwing checked exception
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant