You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2010/03/02 07:03:27 UTC
[jira] Resolved: (BUILDR-232) buildr should print the class of an
exception, not just its message
[ https://issues.apache.org/jira/browse/BUILDR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert resolved BUILDR-232.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.4
Patch applied. Thanks Antoine, that'll be one more beer I'll owe you!
Sending CHANGELOG
Sending lib/buildr/core/application.rb
Sending spec/core/application_spec.rb
Transmitting file data ...
Committed revision 917886.
> buildr should print the class of an exception, not just its message
> -------------------------------------------------------------------
>
> Key: BUILDR-232
> URL: https://issues.apache.org/jira/browse/BUILDR-232
> Project: Buildr
> Issue Type: Wish
> Affects Versions: 1.3.2
> Reporter: Ittay Dror
> Fix For: 1.4
>
> Attachments: BUILDR-232.txt
>
>
> In Java in particular, the class of the exception may mean more than it's message (e.g., NullPointerException has no message). but in standard_exception_handling only the message is printed. (my scenario was that trying to run javac resulted in a message: com/sun/tools/javac/Main which was meaningless to me. adding a print of the class showed it was NoClassDefFoundError, which explained that the environment is not set up correctly)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.