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

Make reading manifest file optional in AnalysisScopeReader #485

Open
coder-chenzhi opened this issue May 9, 2019 · 0 comments · May be fixed by #486
Open

Make reading manifest file optional in AnalysisScopeReader #485

coder-chenzhi opened this issue May 9, 2019 · 0 comments · May be fixed by #486

Comments

@coder-chenzhi
Copy link

AnalysisScopeReader will read the manifest file of jar file and add the Class-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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant