[
http://jira.codehaus.org/browse/MGROOVY-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed MGROOVY-33.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.0-alpha-3
> Allow optional handling of AssertionError (which is produced by Groovy's
> assert keyword) to omit evil stacktrace
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MGROOVY-33
> URL: http://jira.codehaus.org/browse/MGROOVY-33
> Project: Maven 2.x Groovy Plugin
> Issue Type: Improvement
> Components: execute
> Affects Versions: 1.0-alpha-1, 1.0-alpha-2
> Reporter: Jason Dillon
> Assignee: Jason Dillon
> Priority: Minor
> Fix For: 1.0-alpha-3
>
>
> Groovy will always throw an AssertionError if an assert fails regardless of
> the JVM's settings for handling assertions. Its common practice to use
> assert to handle configuration error muck, so the groovy:execute goal should
> by default translate AssertionError into a MojoExecutionException.
--
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 from this list please visit:
http://xircles.codehaus.org/manage_email
