You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andreas Pieber (JIRA)" <ji...@apache.org> on 2012/05/08 16:01:52 UTC
[jira] [Resolved] (KARAF-1448) diag command should print the full
stacktrace instead of the messages only
[ https://issues.apache.org/jira/browse/KARAF-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Pieber resolved KARAF-1448.
-----------------------------------
Resolution: Fixed
Committing to https://svn.apache.org/repos/asf/karaf/trunk ...
M bundle/core/src/main/java/org/apache/karaf/bundle/core/internal/BlueprintListener.java
Committed r1335528
> diag command should print the full stacktrace instead of the messages only
> --------------------------------------------------------------------------
>
> Key: KARAF-1448
> URL: https://issues.apache.org/jira/browse/KARAF-1448
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 3.0.0
> Reporter: Andreas Pieber
> Assignee: Andreas Pieber
> Fix For: 3.0.0
>
>
> Well, since I ran in exactly that problem and was absolutely unable to find out what to do with the message alone I consider it pretty useful printing the full stacktrace instead of the messages only. IMHO the diag command is only really useful during development anyhow (what should a customer do with blueprint error messages/errors); therefore the more information we can provide the better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira