Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Clover plugin produces garbled reports for source code with UTF-8

Petter Måhlén December 18, 2011

Hi,


When the source code contains a line such as:

* @author Petter Måhlén

The corresponding file in the coverage report from running mvn clover2:clover is:

* @author Petter Måhlén

This is in spite of having configured the clover2 plugin like so:

<plugin>
        <groupId>com.atlassian.maven.plugins</groupId>
        <artifactId>maven-clover2-plugin</artifactId>
        <configuration>
          <charset>${default.encoding}</charset>
...

The default.encoding is of course set to UTF-8 and is the setting that is used

for all other plugins.

Any idea if that is a bug (seem not to be allowed to view any bugs, or they've all been moved),

or if it can be fixed somehow?

Thanks,

Petter


1 answer

1 accepted

0 votes
Answer accepted
Nick
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 21, 2012

Hi Petter,

For the maven-clover2-plugin, try setting the 'encoding' configuration instead.

See also: http://docs.atlassian.com/maven-clover2-plugin/3.1.3/setup-mojo.html#encoding

Cheers,

Nick

Petter Måhlén January 22, 2012

That solved it, thanks - we must have been looking here: http://docs.atlassian.com/maven-clover2-plugin/3.1.3/clover-mojo.html when we found the 'charset' parameter.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events