qulice
qulice copied to clipboard
Failed to load PMD resources on multi-threaded maven build
Oct 05, 2018 11:10:03 AM net.sourceforge.pmd.RulesetsFactoryUtils getRuleSets
SEVERE: Ruleset not found
net.sourceforge.pmd.RuleSetNotFoundException: Can't find resource 'category/java/errorprone.xml' for rule 'AvoidDuplicateLiterals'. Make sure the resource is a valid file or URL and is on the CLASSPATH. Here's the current classpath: /home/me/.asdf/installs/maven/3.5.0/boot/plexus-classworlds-2.5.2.jar
at net.sourceforge.pmd.RuleSetReferenceId.getInputStream(RuleSetReferenceId.java:405)
at net.sourceforge.pmd.RuleSetFactory.parseRuleSetNode(RuleSetFactory.java:330)
at net.sourceforge.pmd.RuleSetFactory.createRuleSet(RuleSetFactory.java:214)
at net.sourceforge.pmd.RuleSetFactory.createRule(RuleSetFactory.java:313)
at net.sourceforge.pmd.RuleSetFactory.parseRuleReferenceNode(RuleSetFactory.java:609)
at net.sourceforge.pmd.RuleSetFactory.parseRuleNode(RuleSetFactory.java:463)
at net.sourceforge.pmd.RuleSetFactory.parseRuleSetNode(RuleSetFactory.java:367)
at net.sourceforge.pmd.RuleSetFactory.createRuleSet(RuleSetFactory.java:214)
at net.sourceforge.pmd.RuleSetFactory.createRuleSet(RuleSetFactory.java:209)
at net.sourceforge.pmd.RuleSetFactory.createRuleSets(RuleSetFactory.java:170)
at net.sourceforge.pmd.RuleSetFactory.createRuleSets(RuleSetFactory.java:154)
at net.sourceforge.pmd.RulesetsFactoryUtils.getRuleSets(RulesetsFactoryUtils.java:38)
at net.sourceforge.pmd.processor.AbstractPMDProcessor.createRuleSets(AbstractPMDProcessor.java:68)
at net.sourceforge.pmd.processor.AbstractPMDProcessor.processFiles(AbstractPMDProcessor.java:101)
at net.sourceforge.pmd.PMD.processFiles(PMD.java:329)
at com.qulice.pmd.SourceValidator.validateOne(SourceValidator.java:136)
at com.qulice.pmd.SourceValidator.validate(SourceValidator.java:102)
at com.qulice.pmd.PmdValidator.validate(PmdValidator.java:70)
at com.qulice.maven.CheckMojo$ValidatorCallable.call(CheckMojo.java:235)
at com.qulice.maven.CheckMojo$ValidatorCallable.call(CheckMojo.java:203)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Sometimes it fails with on Can't find resource 'category/java/documentation.xml' for rule 'null'
qulice version 0.18.2
$ mvn -v
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T22:39:06+03:00)
Maven home: /home/me/.asdf/installs/maven/3.5.0
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /home/m/.asdf/installs/java/8.151/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-36-generic", arch: "amd64", family: "unix"
@krzyk/z please, pay attention to this issue
@longtimeago/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!
upgrade to PMD 6.8.0 could help
nah ... tried locally to upgrade PMD to 6.8.0 - the issue is still there :(
@longtimeago does it fail always? I tried it on other projects and haven't seen such error. Maybe there is some specific code that causes it?
@krzyk not always but 2 out of 3. We have >20 top-level maven modules with 1-4 sub-modules per each.
And running maven with following params mvn -T 8 -B -Ddependency.locations.enabled=false verify
it works fine with qulice 0.17.2
@longtimeago Now I noticed it, multithreaded maven build. OK, that I didn't test.
@0crat in
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@0crat in (here)
@krzyk Thanks for your contribution, @longtimeago/z! If you would be a member of the project, you would now earn +15 reputation points, as explained in §29. You can join and apply to it, see §2.
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@krzyk Looks like it has already been resolved in 0.17.2 (https://github.com/teamed/qulice/issues/933#issuecomment-427299920)
@paulodamaso It is a regression, in 0.17.2 it worked but the bug report is for 0.18.2
@krzyk Could not reproduce the problem
@0crat refuse
@0crat refuse (here)
@paulodamaso The user @paulodamaso/z resigned from #933, please stop working. Reason for job resignation: Order was cancelled
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@krzyk/z everybody who has role DEV
is banned at #933; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)