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

Inefficient execution of PMD within eclipse #49

Open
adangel opened this issue May 17, 2018 · 0 comments · Fixed by #55
Open

Inefficient execution of PMD within eclipse #49

adangel opened this issue May 17, 2018 · 0 comments · Fixed by #55
Assignees

Comments

@adangel
Copy link
Member

adangel commented May 17, 2018

There are several issues currently:

  • A new PMD configuration is used per file
  • Each PMD configuration uses an own classloader for the auxclasspath. This leads to inefficient memory usage - the classloader should be shared within the project. This leads to OutOfMemory errors in bigger projects.
  • No multi-thread usage is used, each file is executed after another. If we know, that we want to execute multiple files (e.g. a whole project), we could execute PMD once with the list of files. Via Report/Renderer we can still monitor the progress file by file.
  • If multiple projects are in the workspace, the log messages don't indicate, for which project PMD is currently executed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant