Bean shell enforcer swallows message

The message does not display in the console, because the original EnforcerRuleException is wrapped into another one:

throw new EnforcerRuleException( this.message );
}
}
catch ( Exception e )

{ throw new EnforcerRuleException( "Unable to lookup a component", e ); }

and the console does not display root causes (even with -e, the root cause does not show), living us with "Unable to lookup a component" as an explanation of the rule violation:

[INFO] Scanning for projects...
[INFO] ----------------------------------------------------------------------------
[INFO] Building xxx
[INFO] task-segment: [clean, install]
[INFO] ----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory xxx
[INFO] [enforcer:enforce

{execution: enforce-beanshell}

]
[WARNING] Rule 0: org.apache.maven.plugin.enforcer.EvaluateBeanshell failed with message: Unable to lookup a component
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Oct 04 12:00:25 PDT 2007
[INFO] Final Memory: 6M/12M
[INFO] ------------------------------------------------------------------------