re-opening to provide a fix version

Hi Sebastien,

Thanks for reporting this - the feedback helped us improve the documentation and will hopefully make this clearer for future users.

You will indeed need the licenseLocation in the reporting section's configuration as well.

Please let me know if there is anything else we can do to help.

Best Regards,
Nick Pellow

thanks. it works well like that. Sorry for the confusion, I just followed
the steps on the web site.

Should I put the license in the reporting for build ?

that what I have now
<reporting>
....
<plugin>
<groupId>com.atlassian.maven.plugins</groupId>
<artifactId>maven-clover2-plugin</artifactId>
<configuration>

<licenseLocation>clover.license</licenseLocation>
</configuration>
</plugin>
...

2008/11/11 Nick Pellow [Atlassian] (JIRA) <jira@atlassian.com>

Hi Sebastien,

Sorry for the confusion here. You do not need to modify your settings.xml at all to use the maven-clover2-plugin.
You can simply bind the clover2 goals directly in the pom.xml like this:

                          <build>
                <plugins>
                    <plugin>
                        <groupId>com.atlassian.maven.plugins</groupId>
                        <artifactId>maven-clover2-plugin</artifactId>
                        <version>${cloverVersion}</version>                        
                        <executions>
                            <execution>
                                <id>clover</id>
                                <phase>pre-site</phase>
                                <goals>
                                    <goal>instrument</goal>
                                </goals>
                            </execution>
                        </executions>
                    </plugin>
                </plugins>
        </build>
             <reporting>
                 <plugins>
                     <plugin>
                         <groupId>com.atlassian.maven.plugins</groupId>
                         <artifactId>maven-clover2-plugin</artifactId>
                         <version>${cloverVersion}</version>
                     </plugin>
                 </plugins>
             </reporting>

If you then run mvn site, Clover will run, and a report will be attached to the site docs.

I will try and make this clearer in the online documentation.

Please keep me posted with how you get on.
Cheers,
Nick

in the #1 part of the page your gave me (that's where I got the setup to do)

step 1
Set up your .m2/settings.xml by adding:
.m2/settings.xml
...
<pluginGroups>
<pluginGroup>com.atlassian.maven.plugins</pluginGroup>
</pluginGroups>
...
and in the issues tracker you said :
There is no way in maven to supply the pluginGroup anywhere but the
settings.xml .
The maven-clover2-plugin may be used however via the pom.xml if adding the
pluginGroup to each settings.xml is a hassle.

so I assume that IF I don't want to edit settings.xml I can't use clover2
right ? (and why clover1 works ? )

I talked with the group and we don'T want to edit settings.xml, so if it's
the only option, we will have to pass and stick with cobertura.

There is no way in maven to supply the pluginGroup anywhere but the settings.xml .

The maven-clover2-plugin may be used however via the pom.xml if adding the pluginGroup to each settings.xml is a hassle.

Hi Sebastien,

The Clover2 maven plugin is already at maven central: http://repo1.maven.org/maven2/com/atlassian/maven/plugins/maven-clover2-plugin/ .
The problem is, the groupId has to be com.atlassian.maven.plugins as the source code is hosted at Atlassian now.

You should not need to update all users ~/.m2/settings.xml to have the maven-clover2-plugin integrated into your build. Simply add the clover2 plugin definition to the pom.xml and bind each goal to an execution.

Please read the documentation on Running Clover from the Pom.

Please let me know if you have any questions or problems getting this going.

Best Regards,
Nick Pellow.