-
Notifications
You must be signed in to change notification settings - Fork 220
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
Make reading manifest file optional in AnalysisScopeReader #485
Comments
coder-chenzhi
pushed a commit
to coder-chenzhi/WALA
that referenced
this issue
May 9, 2019
coder-chenzhi
added a commit
to coder-chenzhi/WALA
that referenced
this issue
May 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AnalysisScopeReader
will read the manifest file of jar file and add theClass-Path
entries into scope, by default. However, the class-path specification is for use when executing Java applications via the "java -jar" command. It doesn't apply to webapps (WARs). Actually, FileNotfoundException will throw up when I use WALA to analyze some large-scale WARS.And I am working on to solve this problem by adding some extra method into
AnalysisScopeReader
. When it is ready, I will create a PR.The text was updated successfully, but these errors were encountered: