You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Neal Sanche (JIRA)" <ji...@apache.org> on 2006/06/23 05:33:29 UTC
[jira] Created: (GERONIMODEVTOOLS-86) Stack Traces upon Publishing
Errors are difficult to read
Stack Traces upon Publishing Errors are difficult to read
---------------------------------------------------------
Key: GERONIMODEVTOOLS-86
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-86
Project: Geronimo-Devtools
Type: Improvement
Components: eclipse-plugin
Environment: Windows, Eclipse Callisto RC4a.
Reporter: Neal Sanche
The stack traces produced when the eclipse plugin fails to deploy a project to the server appear all on one line, so that the developer has to scroll horizontally to find the cause of the problem. An improvement I would suggest would be to present the user the Message text of the exception and all of the CausedBy exceptions first, then rewrite the stacktrace to provide the correct line-breaks for the platform before displaying it to the user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMODEVTOOLS-86) Stack Traces upon Publishing
Errors are difficult to read
Posted by "Sachin Patel (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-86?page=all ]
Sachin Patel updated GERONIMODEVTOOLS-86:
-----------------------------------------
Fix Version/s: 1.x
> Stack Traces upon Publishing Errors are difficult to read
> ---------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-86
> URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-86
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Environment: Windows, Eclipse Callisto RC4a.
> Reporter: Neal Sanche
> Fix For: 1.x
>
>
> The stack traces produced when the eclipse plugin fails to deploy a project to the server appear all on one line, so that the developer has to scroll horizontally to find the cause of the problem. An improvement I would suggest would be to present the user the Message text of the exception and all of the CausedBy exceptions first, then rewrite the stacktrace to provide the correct line-breaks for the platform before displaying it to the user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMODEVTOOLS-86) Stack Traces upon Publishing
Errors are difficult to read
Posted by "Sachin Patel (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-86?page=all ]
Sachin Patel closed GERONIMODEVTOOLS-86.
----------------------------------------
Resolution: Fixed
Should be fixed now, though GERONIMODEVTOOLS-90.
> Stack Traces upon Publishing Errors are difficult to read
> ---------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-86
> URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-86
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Environment: Windows, Eclipse Callisto RC4a.
> Reporter: Neal Sanche
> Assigned To: Sachin Patel
> Fix For: 1.x
>
>
> The stack traces produced when the eclipse plugin fails to deploy a project to the server appear all on one line, so that the developer has to scroll horizontally to find the cause of the problem. An improvement I would suggest would be to present the user the Message text of the exception and all of the CausedBy exceptions first, then rewrite the stacktrace to provide the correct line-breaks for the platform before displaying it to the user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMODEVTOOLS-86) Stack Traces upon Publishing
Errors are difficult to read
Posted by "Sachin Patel (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-86?page=all ]
Sachin Patel reassigned GERONIMODEVTOOLS-86:
--------------------------------------------
Assignee: Sachin Patel
> Stack Traces upon Publishing Errors are difficult to read
> ---------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-86
> URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-86
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Environment: Windows, Eclipse Callisto RC4a.
> Reporter: Neal Sanche
> Assigned To: Sachin Patel
> Fix For: 1.x
>
>
> The stack traces produced when the eclipse plugin fails to deploy a project to the server appear all on one line, so that the developer has to scroll horizontally to find the cause of the problem. An improvement I would suggest would be to present the user the Message text of the exception and all of the CausedBy exceptions first, then rewrite the stacktrace to provide the correct line-breaks for the platform before displaying it to the user.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira