[
http://jira.codehaus.org/browse/MOJO-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208237#action_208237
]
Tamsin Slinn commented on MOJO-1443:
------------------------------------
Hi Daan,
Thanks for the suggestion - I removed some uppercase letters from the report
file, but that didn't help.
So I checked out the source for the plugin, added an e.printStackTrace,
installed a version of the plugin in my local repository and found the problem
was not having java/javac in my path (just had JAVA_HOME set).
I did try the suggestion in your original comment but I think that needs a
later version of the Maven Plugin API.
Cheers,
Tamsin
> Allow exceptions to be thrown instead of wrapping the exception message
> -----------------------------------------------------------------------
>
> Key: MOJO-1443
> URL: http://jira.codehaus.org/browse/MOJO-1443
> Project: Mojo
> Issue Type: Bug
> Components: jasperreports
> Reporter: Daan Gerits
>
> When compiling the jasper reports, all JRExceptions and
> InclusionScanExceptions will be catched and their message will be wrapped
> into a MojoFailedException. A lot of information about the catched exception
> is lost this way. Maybe it is better to wrap the whole catched exception
> instead of just it's message.
--
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
