Inefficient execution of PMD within eclipse
Open
@adangel is already working on this.
Since Jul 31, 2018.
enhancement
- Dominant language
- Java
- Stars
- 99
- Forks
- 42
- Avg merge
- 20h 19m
- Merged PRs (30d)
- 19
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.