You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org> on 2008/01/04 19:02:44 UTC

[jira] Created: (TAPESTRY-2015) Improve stacktraces in exception page

Improve stacktraces in exception page
-------------------------------------

                 Key: TAPESTRY-2015
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
             Project: Tapestry
          Issue Type: Improvement
    Affects Versions: 5.0.7
            Reporter: Andreas Andreou
            Priority: Minor


Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
- Use monospace for the stacktraces
- Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
add a class to the related LI (you won't be able to live without this once you have it)
- Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Andreou updated TAPESTRY-2015:
--------------------------------------

    Assignee:     (was: Andreas Andreou)

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Priority: Minor
>             Fix For: 5.0.11
>
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Kevin Menard (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556013#action_12556013 ] 

Kevin Menard commented on TAPESTRY-2015:
----------------------------------------

Another nifty thing would be if the Tapestry classes were clickable links.  They could either open up sources downloaded from maven or go directly to the ViewVC instance at Apache.

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Priority: Minor
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Reopened: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reopened TAPESTRY-2015:
--------------------------------------------

      Assignee: Andreas Andreou

Good ideas, I came up with one (highlight app classes) independently.

Why is this marked fixed?  I can't find any indication that any work occured on it.

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Assignee: Andreas Andreou
>            Priority: Minor
>             Fix For: 5.0.11
>
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-2015:
-------------------------------------------

    Fix Version/s:     (was: 5.0.11)
                   5.0.12

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Priority: Minor
>             Fix For: 5.0.12
>
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Massimo Lusetti (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556536#action_12556536 ] 

Massimo Lusetti commented on TAPESTRY-2015:
-------------------------------------------

Having user classes hightlighted would be neat!

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Priority: Minor
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAP5-101) Improve stacktraces in exception page

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-101:
--------------------------------------

    Issue Type: Improvement  (was: Bug)

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAP5-101
>                 URL: https://issues.apache.org/jira/browse/TAP5-101
>             Project: Tapestry 5
>          Issue Type: Improvement
>            Reporter: Andreas Andreou
>            Priority: Minor
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-2015:
-------------------------------------------

    Fix Version/s:     (was: 5.0.13)
                   5.0

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Priority: Minor
>             Fix For: 5.0
>
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-2015:
-------------------------------------------

    Fix Version/s:     (was: 5.0.12)
                   5.0.13

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Priority: Minor
>             Fix For: 5.0.13
>
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Assigned: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Kevin Menard (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Menard reassigned TAPESTRY-2015:
--------------------------------------

    Assignee: Kevin Menard

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Assignee: Kevin Menard
>            Priority: Minor
>             Fix For: 5.0
>
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621698#action_12621698 ] 

Howard M. Lewis Ship commented on TAPESTRY-2015:
------------------------------------------------

Ohter ideas:
- Add a check box to make "hidden" stack frames visible or not (i.e., render them with an invisible style, toggle visibility using JavaScript).
- Allow a configuration of regexps to identify what is hidden, what is user code, what is tapestry code, etc.

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Assignee: Kevin Menard
>            Priority: Minor
>             Fix For: 5.0
>
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Resolved: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Andreou resolved TAPESTRY-2015.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.11

Seems fixed by https://issues.apache.org/jira/browse/TAPESTRY-2222

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Priority: Minor
>             Fix For: 5.0.11
>
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-2015) Improve stacktraces in exception page

Posted by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574321#action_12574321 ] 

Andreas Andreou commented on TAPESTRY-2015:
-------------------------------------------

i thought TAP-2222 was really a duplicate - but i guess i had asked for more here :)

> Improve stacktraces in exception page
> -------------------------------------
>
>                 Key: TAPESTRY-2015
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2015
>             Project: Tapestry
>          Issue Type: Improvement
>    Affects Versions: 5.0.7
>            Reporter: Andreas Andreou
>            Assignee: Andreas Andreou
>            Priority: Minor
>             Fix For: 5.0.11
>
>
> Here are my suggestions (based on related work on T4 @ TAPESTRY-1787):
> - Use monospace for the stacktraces
> - Highlight user classes... we know them from the tapestry.app-package parameter and we just have to 
> add a class to the related LI (you won't be able to live without this once you have it)
> - Highlight tapestry classes. I'm guessing this one will be useful as well

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org