[ http://jira.codehaus.org/browse/MNG-1136?page=all ]
Dave Sag updated MNG-1136:
--------------------------
Attachment: maven-clover-plugin-samples_breaks_DS.zip
Okay i found something. Firstly I didn't realise that you have to configure
plugins twice, once in the build section and then again in the reports section.
But secondly, when I use asserts I use the following syntax:
assert true == true : "true was not true";
rather than as you had it assert (true == true);
both are valid Java, but clover jams on the first. I suspect this is a bug in
clover, not the plugin.
> 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
> 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]
