Is Sonar kicked off by the Jenkins plugin? If so, I think something may not be configured properly. The current code in Sonar does not match the latest Jenkins builds...
-Matt On 4/18/11 9:12 AM, "Ate Douma" <[email protected]> wrote: >See: https://analysis.apache.org/dashboard/index/58996 > >-------- Original Message -------- >Subject: [jira] [Closed] (INFRA-3586) Add Rave (Incubating) to Sonar >Date: Mon, 18 Apr 2011 12:31:06 +0000 (UTC) >From: Olivier Lamy (JIRA) <[email protected]> >Reply-To: [email protected] >To: [email protected] > > > [ >https://issues.apache.org/jira/browse/INFRA-3586?page=com.atlassian.jira.p >lugin.system.issuetabpanels:all-tabpanel >] > >Olivier Lamy closed INFRA-3586. >------------------------------- > > Resolution: Fixed > >done. >first analysis finished. > >> Add Rave (Incubating) to Sonar >> ------------------------------ >> >> Key: INFRA-3586 >> URL: https://issues.apache.org/jira/browse/INFRA-3586 >> Project: Infrastructure >> Issue Type: Task >> Security Level: public(Regular issues) >> Components: Analysis >> Reporter: Ate Douma >> Assignee: Olivier Lamy >> >> Details based on the template from INFRA-3402: >> * svnurl : http://svn.apache.org/repos/asf/incubator/rave/rave-trunks/ >> * pom path : (blank as svnurl/pom.xml) >> * maven version : 3+ >> * jdk version : 1.6+ >> * maven profiles to use : >> * maven build properties : > >-- >This message is automatically generated by JIRA. >For more information on JIRA, see: http://www.atlassian.com/software/jira
