
IDE plugins can create ClassLoaders representing the "project" settings in the IDE, providing PMD with that ClassLoader, such that PMD can truly see the classes being represented in the IDE. In the specific case of Eclipse, the IDE plugin runs in a ClassLoader which does not contain the details of the "project" settings, which means without this feature PMD would never be able to do proper Type Resolution. I've not had a chance to benchmark this change. I expect there to be some performance changes given that 'static' reference to the PMDASMClassLoader is no longer used. Further tuning may need to be done. git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@5819 51baf565-9d33-0410-a72c-fc3788e3496d
…
…
…
…
Description
Languages
Java
75.5%
Apex
9.7%
Kotlin
9.1%
ANTLR
2.7%
PLSQL
1%
Other
1.8%