sonarqube5.1 - What to do if sonarqube fails due to negative SQALE density value -


we have upgraded sonarqube 5.1 , analyze our huge multi-module project using maven. while several runs analysis successful, since days get:

[error] failed execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project jahia-dev-root: sqale density value should between 0 , 1.7976931348623157e308 , got -0.004 -> [help 1] org.apache.maven.lifecycle.lifecycleexecutionexception: failed execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project jahia-dev-root: sqale density value should between 0 , 1.7976931348623157e308 , got -0.004 @ org.apache.maven.lifecycle.internal.mojoexecutor.execute(mojoexecutor.java:217) @ org.apache.maven.lifecycle.internal.mojoexecutor.execute(mojoexecutor.java:153) @ org.apache.maven.lifecycle.internal.mojoexecutor.execute(mojoexecutor.java:145) @ org.apache.maven.lifecycle.internal.lifecyclemodulebuilder.buildproject(lifecyclemodulebuilder.java:84) @ org.apache.maven.lifecycle.internal.lifecyclemodulebuilder.buildproject(lifecyclemodulebuilder.java:59) @ org.apache.maven.lifecycle.internal.lifecyclestarter.singlethreadedbuild(lifecyclestarter.java:183) @ org.apache.maven.lifecycle.internal.lifecyclestarter.execute(lifecyclestarter.java:161) @ org.apache.maven.defaultmaven.doexecute(defaultmaven.java:320) @ org.apache.maven.defaultmaven.execute(defaultmaven.java:156) @ org.apache.maven.cli.mavencli.execute(mavencli.java:537) @ org.apache.maven.cli.mavencli.domain(mavencli.java:196) @ org.apache.maven.cli.mavencli.main(mavencli.java:141) @ sun.reflect.nativemethodaccessorimpl.invoke0(native method) @ sun.reflect.nativemethodaccessorimpl.invoke(nativemethodaccessorimpl.java:57) @ sun.reflect.delegatingmethodaccessorimpl.invoke(delegatingmethodaccessorimpl.java:43) @ java.lang.reflect.method.invoke(method.java:606) @ org.codehaus.plexus.classworlds.launcher.launcher.launchenhanced(launcher.java:290) @ org.codehaus.plexus.classworlds.launcher.launcher.launch(launcher.java:230) @ org.codehaus.plexus.classworlds.launcher.launcher.mainwithexitcode(launcher.java:409) @ org.codehaus.plexus.classworlds.launcher.launcher.main(launcher.java:352) caused by: org.apache.maven.plugin.mojoexecutionexception: sqale density value should between 0 , 1.7976931348623157e308 , got -0.004 @ org.codehaus.mojo.sonar.bootstrap.exceptionhandling.handle(exceptionhandling.java:41) @ org.codehaus.mojo.sonar.bootstrap.runnerbootstraper.execute(runnerbootstraper.java:139) @ org.codehaus.mojo.sonar.sonarmojo.execute(sonarmojo.java:132) @ org.apache.maven.plugin.defaultbuildpluginmanager.executemojo(defaultbuildpluginmanager.java:101) @ org.apache.maven.lifecycle.internal.mojoexecutor.execute(mojoexecutor.java:209) ... 19 more caused by: sqale density value should between 0 , 1.7976931348623157e308 , got -0.004 

from log last sub-module analyzed webapp without java files, groovy, jsp, javascript , xml files. has idea, if there workaround or how proceed solving problem? have upgraded plugins java 3.3, groovy 1.1.1, xml 1.3 last week. related?

update 14.07.2015: found switching default xml profile 0 rules activated solved problem. before had following xml rules active:

  • newlines should follow each element
  • source code should indented consistently
  • tabulation characters should not used

i still don't know why activating these xml rules runs exception.


Comments

Popular posts from this blog

searchKeyword not working in AngularJS filter -

sequelize.js - Sequelize: sort by enum cases -

user interface - how to replace an ongoing process of image capture from another process call over the same ImageLabel in python's GUI TKinter -