[ http://jira.codehaus.org/browse/MNG-1136?page=comments#action_49027 ] 

Matthew Beermann commented on MNG-1136:
---------------------------------------

I have exactly the plugin configuration mentioned above, and I'm trying to 
instrument a code that contains an assertion. Nothing wierd about the use 
case...

Neither -jdk14 or -jdk15 is stated as being the default in the documentation 
link above; so if Clover is trying to instrument my code using 1.3 syntax, it's 
dying correctly AFAICT.

> 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

>
>
> 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]

Reply via email to