The following comment has been added to this issue:
Author: Mark Wilkinson
Created: Wed, 20 Aug 2003 6:20 AM
Body:
jexl has been patched to rethrow exceptions thrown by methods called from ASTMethod,
but there's some debugging code remaining that dumps a stack trace to System.out. I've
reopened http://issues.apache.org/bugzilla/show_bug.cgi?id=20729 to get this last bit
resolved.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-380
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-380
Summary: jexl swallows exceptions and thus maven builds can go awry
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: 4 hours
Project: maven
Components:
core
Fix Fors:
1.0-beta-9
1.1
Versions:
1.0-beta-9
Assignee:
Reporter: Ben Walding
Created: Mon, 7 Apr 2003 5:55 AM
Updated: Wed, 20 Aug 2003 1:49 AM
Description:
If a jexl expression has an exception (eg.
${pojo.methodThatFailsBadly()}, the exception is swallowed in ASTMethod
around line 58 (this is in the jexl library).
Its failure gives a useless message, then the build continues on it's merry way,
ignoring any testing problems that might have occurred.
I propose that we patch jexl (I don't know enough about AST generation to do it
easily) such that exceptions can be propagated (wrapped into runtimeexceptions if
needs be).
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
