Hi Thomas,
according to the description at
http://docs.codehaus.org/display/SONAR/Analyzing+Java+Projects you
definitely need a pom.xml to get sonar working.
exporting and manipulating a pom.xml with gradle is easy. you can start
with this snippet:
--------------
apply plugin:'java'
apply plugin:'maven'
group = 'org.acme'
version = '0.1-SNAPSHOT'
def SONAR_PROP_DYN_ALIAS = """\
<properties>
<sonar.dynamicAnalysis>false</sonar.dynamicAnalysis>
</properties>
"""
task exportPom << {
pom {
withXml { xmlProvider ->
def xml = xmlProvider.asString()
xml.insert(xml.lastIndexOf('</project>'),
SONAR_PROP_DYN_ALIAS)
}
}.writeTo("pom.xml")
}
--------------
regards,
René
ps.: I had a look on the sonar mvn plugin. maybe we could port it to
support gradle more nativly. any volunteers?
bye bye
Am 18.10.10 20:26, schrieb Thomas Carlier:
> Hi Rene:
>
> That's what I've found out so far. I've been hoping to find a gradle plugin
> that would make the necessary maven calls to Sonar. Otherwise, I'm thinking
> it would be nice to have an 'export to pom.xml' command within gradle so we
> wouldn't have to maintain 2 configuration files, just to use Sonar. (yes,
> we really want to use Sonar *and* stay with gradle).
>
> I hope someone can help me find my way through the maze of (what seems to
> be) disconnected technologies.
>
> Thanks,
>
> --- Tom C.
>
> On Sat, Oct 16, 2010 at 5:26 AM, Rene Groeschke <[email protected]> wrote:
>
>> Hi Tom,
>> sorry, I've mixed up Sonar and Nexus by Sonartype. I think you mean
>> http://www.sonarsource.org/. I can't find an API description on how to
>> deploy your measures to Sonar. It seems to be hardly wired with maven.
>>
>> regards,
>> René
>>
>>
>> Am 16.10.10 13:29, schrieb Thomas Carlier:
>>> Hi Rene:
>>>
>>> Sonar is not an artifact repository. It's an open source quality
>> management
>>> platform, dedicated to continuously analyze and measure technical
>> quality,
>>> from the project portfolio to the class method.
>>>
>>> I'd like to use it for tracking the emma code coverage trends over time
>> (and
>>> other code health metrics).
>>>
>>> --- Tom C.
>>>
>>> On Thu, Oct 14, 2010 at 8:26 PM, Rene Groeschke <[email protected]>
>> wrote:
>>>> Hi Thomas,
>>>>
>>>> there was a discussion on how to do handle/upload a custom produced file
>>>> (DLL in this example) with gradle and artifactory on this mailinglist.
>>>> Take a look at
>>>> http://markmail.org/message/niseybxbjynckr2c
>>>>
>>>> regards,
>>>> René
>>>>
>>>> Am 15.10.10 02:40, schrieb Thomas Carlier:
>>>>> I have my gradle build producing emma code coverage reports and I'd
>> like
>>>> to
>>>>> upload them to a Sonar server.
>>>>>
>>>>> Can anyone help me understand the syntax for this?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --- Tom C.
>>>>>
>>>> --
>>>> ------------------------------------
>>>> Rene Groeschke
>>>>
>>>> [email protected]
>>>> http://www.breskeby.com
>>>> http://twitter.com/breskeby
>>>> ------------------------------------
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>> http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>
>> --
>> ------------------------------------
>> Rene Groeschke
>>
>> [email protected]
>> http://www.breskeby.com
>> http://twitter.com/breskeby
>> ------------------------------------
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
--
------------------------------------
Rene Groeschke
[email protected]
http://www.breskeby.com
http://twitter.com/breskeby
------------------------------------
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
