sonarqube - sonar 4.5.4-- Debt definition of rule is invalid exception -


i have own customized plugins of csharp of version 2.1 when deployed stylecope plugin in sonar 4.5.4 server, rules getting exception below after removing rule working fine. exception getting in sonar 4.5.4 not facing issues in sonar 4.2 , lesser version. need know why issue occuring , mean say? please explain. thanks

java.lang.illegalargumentexception: debt definition on rule 'stylecopcsharp:constfieldnamesmustbeginwithuppercaseletter' invalid @ org.sonar.server.rule.deprecatedrulesdefinitionloader.remediationfunction(deprecatedrulesdefinitionloader.java:135) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.rule.deprecatedrulesdefinitionloader.updateruledebtdefinitions(deprecatedrulesdefinitionloader.java:117) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.rule.deprecatedrulesdefinitionloader.complete(deprecatedrulesdefinitionloader.java:107) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.rule.ruledefinitionsloader.load(ruledefinitionsloader.java:53) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.rule.registerrules.start(registerrules.java:102) ~[sonar-server-4.5.4.jar:na] @ sun.reflect.nativemethodaccessorimpl.invoke0(native method) ~[na:1.7.0_55] @ sun.reflect.nativemethodaccessorimpl.invoke(unknown source) ~[na:1.7.0_55] @ sun.reflect.delegatingmethodaccessorimpl.invoke(unknown source) ~[na:1.7.0_55] @ java.lang.reflect.method.invoke(unknown source) ~[na:1.7.0_55] @ org.picocontainer.lifecycle.reflectionlifecyclestrategy.invokemethod(reflectionlifecyclestrategy.java:110) ~[picocontainer-2.14.3.jar:na] @ org.picocontainer.lifecycle.reflectionlifecyclestrategy.start(reflectionlifecyclestrategy.java:89) ~[picocontainer-2.14.3.jar:na] @ org.picocontainer.injectors.abstractinjectionfactory$lifecycleadapter.start(abstractinjectionfactory.java:84) ~[picocontainer-2.14.3.jar:na] @ org.picocontainer.behaviors.abstractbehavior.start(abstractbehavior.java:169) ~[picocontainer-2.14.3.jar:na] @ org.picocontainer.behaviors.stored$realcomponentlifecycle.start(stored.java:132) ~[picocontainer-2.14.3.jar:na] @ org.picocontainer.behaviors.stored.start(stored.java:110) ~[picocontainer-2.14.3.jar:na] @ org.picocontainer.defaultpicocontainer.potentiallystartadapter(defaultpicocontainer.java:1015) ~[picocontainer-2.14.3.jar:na] @ org.picocontainer.defaultpicocontainer.startadapters(defaultpicocontainer.java:1008) ~[picocontainer-2.14.3.jar:na] @ org.picocontainer.defaultpicocontainer.start(defaultpicocontainer.java:766) ~[picocontainer-2.14.3.jar:na] @ org.sonar.api.platform.componentcontainer.startcomponents(componentcontainer.java:92) ~[sonar-plugin-api-4.5.4.jar:na] @ org.sonar.server.platform.servercomponents$1.doprivileged(servercomponents.java:590) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.user.doprivileged.execute(doprivileged.java:43) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.platform.servercomponents.executestartuptasks(servercomponents.java:586) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.platform.platform.executestartuptasks(platform.java:126) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.platform.platform.startlevel34containers(platform.java:122) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.platform.platform.dostart(platform.java:81) ~[sonar-server-4.5.4.jar:na] @ org.sonar.server.platform.platformservletcontextlistener.contextinitialized(platformservletcontextlistener.java:43) ~[sonar-server-4.5.4.jar:na] @ org.apache.catalina.core.standardcontext.listenerstart(standardcontext.java:4973) [tomcat-embed-core-7.0.54.jar:7.0.54] @ org.apache.catalina.core.standardcontext.startinternal(standardcontext.java:5467) [tomcat-embed-core-7.0.54.jar:7.0.54] @ org.apache.catalina.util.lifecyclebase.start(lifecyclebase.java:150) [tomcat-embed-core-7.0.54.jar:7.0.54] @ org.apache.catalina.core.containerbase$startchild.call(containerbase.java:1559) [tomcat-embed-core-7.0.54.jar:7.0.54] @ org.apache.catalina.core.containerbase$startchild.call(containerbase.java:1549) [tomcat-embed-core-7.0.54.jar:7.0.54] @ java.util.concurrent.futuretask.run(unknown source) [na:1.7.0_55] @ java.util.concurrent.threadpoolexecutor.runworker(unknown source) [na:1.7.0_55] @ java.util.concurrent.threadpoolexecutor$worker.run(unknown source) [na:1.7.0_55] @ java.lang.thread.run(unknown source) [na:1.7.0_55]

the .net , c# plugins version 2.1 not compatible newer versions of sonarqube (including 4.5.4).

you should consider upgrading latest c# plugin , use msbuild sonarqube runner developed in partnership microsoft analyze .net projects: vastly improves experience, provides better analysis results, , way easier use.

see http://redirect.sonarsource.com/plugins/csharp.html started.

the information below informative only, , allow proceed unsupported deprecated version of c# plugin (which bad, think twice :p):

i see created own stylecop plugin, key stylecopcsharp: should define valid sqale remediation costs each rule - or sonarqube refuse start.

the easiest way remove sqale remediation cost information. now, if you'd keep sqale, can have @ stack trace , see how sonarqube's validation works: deprecatedrulesdefinitionloader.java#l135

there more obstacles preventing use of .net , c# sonarqube 4.5.4, again think twice before going way.


-

Comments

Post a Comment

Popular posts from this blog

java - UnknownEntityTypeException: Unable to locate persister (Hibernate 5.0) -

Image
in code below when try execute main.java getting exception: exception in thread "main" org.hibernate.unknownentitytypeexception: unable locate persister: com.np.vta.test.pojo.users @ org.hibernate.internal.sessionfactoryimpl.locateentitypersister(sessionfactoryimpl.java:792) @ org.hibernate.internal.sessionimpl.locateentitypersister(sessionimpl.java:2637) @ org.hibernate.internal.sessionimpl.access$2500(sessionimpl.java:164) @ org.hibernate.internal.sessionimpl$identifierloadaccessimpl.<init>(sessionimpl.java:2575) @ org.hibernate.internal.sessionimpl$identifierloadaccessimpl.<init>(sessionimpl.java:2562) @ org.hibernate.internal.sessionimpl.byid(sessionimpl.java:1044) @ org.hibernate.internal.sessionimpl.get(sessionimpl.java:955) @ com.app.test.main.main(main.java:20) but if uncomment cfg.addclass( users.class ).addresource( "com/np/vta/test/pojo/users.hbm.xml" ); code works fine. why not reading <mapping...
Read more

python - ValueError: empty vocabulary; perhaps the documents only contain stop words -

i'm using (for first time) scikit library , got error: valueerror: empty vocabulary; perhaps documents contain stop words file "c:\users\a605563\desktop\velibprojetpreso\traitementtwitterdico.py", line 33, in <module> x_train_counts = count_vect.fit_transform(filetweets) file "c:\python27\lib\site-packages\sklearn\feature_extraction\text.py", line 804, in fit_transform self.fixed_vocabulary_) file "c:\python27\lib\site-packages\sklearn\feature_extraction\text.py", line 751, in _count_vocab raise valueerror("empty vocabulary; perhaps documents contain stop words but don't understand why that's happening. import sklearn sklearn.feature_extraction.text import countvectorizer import pandas pd import numpy import unicodedata import nltk tweetsfile = open('tweets2015-08-13.csv', 'r+') f2 = open('analyzer.txt', 'a') print tweetsfile.readline() count_vect = countvectorizer(strip_accents='ascii...
Read more

ubuntu - collect2: fatal error: ld terminated with signal 9 [Killed] -

Image
i'm trying build precimonious on ubuntu 16.04.3 x64. allocated 1gb memory it. file structure looks like ~ |--- llvm/ |--- precimonious/ where llvm on version 3.0 mentioned @ https://github.com/corvette-berkeley/precimonious#requirement . followed steps on readme command make ended with ... llvm[1]: linking debug shared library libllvm-3.0.so collect2: fatal error: ld terminated signal 9 [killed] compilation terminated. ... i went through answers online , might because there's not enough memory perform link. memory usage the gcc version on machine gcc version 5.4.0 20160609 (ubuntu 5.4.0-6ubuntu1~16.04.4) , installed via apt-get install build-essential . fresh droplet created on digitalocean btw. appreciated. it memory exhaustion. sampling interval memory measurement not small enough covers exact point oom killer kicks in. depending on container/vm technology, may able set vm.overcommit_memory=2 before build, process not killed (but doing requires m...
Read more