Affects PMD Version:
Commit 9d23d79 (PMD 6.45.0)
Description:
It looks like the Maven dependencies declared by pmd-apex-jorje do not match the actual dependencies of the currently used apex-jorje-lsp.jar anymore. In particular jol-core seems to not be used anymore, and some other dependencies are pulled in as transitive dependencies and might not have to be declared explicitly.
Do you think it would be possible to adjust the create-local-repo.sh script to automatically adjust the pmd-apex-jorje POM with the information from the META-INF/maven directory in the apex-jorje-lsp.jar file? (with exclusions for the com.salesforce.apex artifacts, since they are part of the JAR)
Maybe it would also be good to add a small comment to create-local-repo.sh explaining why com/google/common* is not removed from the JAR. Currently one has to dig into the Git history to find #773 (comment) which mentions that apex-jorje-lsp.jar is using a modified version of Guava.
Affects PMD Version:
Commit 9d23d79 (PMD 6.45.0)
Description:
It looks like the Maven dependencies declared by pmd-apex-jorje do not match the actual dependencies of the currently used
apex-jorje-lsp.jaranymore. In particularjol-coreseems to not be used anymore, and some other dependencies are pulled in as transitive dependencies and might not have to be declared explicitly.Do you think it would be possible to adjust the
create-local-repo.shscript to automatically adjust the pmd-apex-jorje POM with the information from theMETA-INF/mavendirectory in theapex-jorje-lsp.jarfile? (with exclusions for thecom.salesforce.apexartifacts, since they are part of the JAR)Maybe it would also be good to add a small comment to
create-local-repo.shexplaining whycom/google/common*is not removed from the JAR. Currently one has to dig into the Git history to find #773 (comment) which mentions thatapex-jorje-lsp.jaris using a modified version of Guava.