[
https://issues.jboss.org/browse/JBIDE-21602?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-21602:
------------------------------------
Instead of doing maven-based analysis with SonarQube we could switch to running the code
coverage analysis directly.
{quote}Go to the Build section, click on Add build step and choose Invoke Standalone Sonar
Analysis{quote} --
http://docs.sonarqube.org/display/SONARQUBE45/Triggering+SonarQube+on+Hud...
Of course that's for SonarQube 4.5, and we have 2.3 on Jenkins. Maybe we should start
by asking ci-issues@ to upgrade the SonarQube plugin?
Sonar build for openshift is failing
------------------------------------
Key: JBIDE-21602
URL:
https://issues.jboss.org/browse/JBIDE-21602
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.1.Beta2
Reporter: Andre Dietisheim
Assignee: Mickael Istria
Attachments: sonar-build-output.txt
Sonar for openshift is currently failing in our jenkins at
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
I see it complaining in the build about an incompatible bytecode version:
{code}
Caused by: java.lang.UnsupportedClassVersionError:
org/eclipse/tycho/core/p2/P2ArtifactRepositoryLayout : Unsupported major.minor version
51.0
{code}
The full build output is attached [^sonar-build-output.txt]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)