Many many thanks!!!

-----Oorspronkelijk bericht-----
Van: Olivier Lamy [mailto:[email protected]] 
Verzonden: donderdag 18 augustus 2011 12:32
Aan: Maven Developers List
Onderwerp: Re: [PATCH] Maven PMD Plugin / MPMD-127 - Report cannot correctly 
handle external PMD ruleset as exported by Sonar QA Dashboard

Hello,
Done.

Thanks for the patch !
-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

2011/8/18 Tjerk Stroband <[email protected]>:
> Hi all,
>
>
>
> We're using the Maven Site to generate and publish to our intranet. The PMD
> report provides valuable intel on project and code health and we've been
> using it quite successfully for a long time. Recently we decided to
> introduce Sonar to provide additional metrics, trend insight, etc. Sonar
> lets us 'manage' violations in a central repository and publishes the PMD
> rules-config on a url. Unfortunately this results in a temporary filename
> that contains illegal characters.
>
>
>
> http://jira.codehaus.org/browse/MPMD-127
>
>
>
> I've created a patch that replaces these characters with underscores and
> includes a unit-test to verify correct file naming. It's attached to the
> issue (and this email).
>
>
>
> Can anyone integrate the patch into 2.6-SNAPSHOT? I would gladly commit it
> myself but I am not a listed developer on the project.
>
> It's not the most popular issue, nor is it blocking but it would make 3
> voters and 4 watchers very happy...
>
>
>
> Thank you in advance,
>
> Best regards,
>
>
>
> Tjerk Stroband
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to