[ http://jira.codehaus.org/browse/MNG-1136?page=comments#action_49144 ]
Vincent Massol commented on MNG-1136:
-------------------------------------
Thanks Dave. That did it. I've fixed this. You'll now need to specify the jdk
in the plugin's configuraiton. For example:
[...]
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clover-plugin</artifactId>
<configuration>
<jdk>1.4</jdk>
</configuration>
[...]
I don't think you need to configure the plugin twice... The reason it is
configured twice in the sample is because I wanted to test two things (the
clover:check feature and the site report). But you're right I'll split it into
2 examples not to confuse people...
> clover breaks when encountering assert statements.
> --------------------------------------------------
>
> Key: MNG-1136
> URL: http://jira.codehaus.org/browse/MNG-1136
> Project: Maven 2
> Type: Bug
> Components: maven-clover-plugin
> Versions: 2.0-beta-3
> Environment: any
> Reporter: Dave Sag
> Assignee: Vincent Massol
> Fix For: 2.0.1
> Attachments: example_pom_from_davesag.xml,
> maven-clover-plugin-samples-20051024.zip,
> maven-clover-plugin-samples_breaks_DS.zip
>
>
> the clover plugin is breaking on the line
> assert result != null : "the result should not be null";
> saying
> [INFO] Reason: Clover has failed to instrument the source files
> i can only assume that this is because clover does not understand the assert,
> or is assuming java 1.3? eitherway it's no use to me until this is fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
