You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (Created) (JIRA)" <ji...@apache.org> on 2012/01/06 17:42:39 UTC
[jira] [Created] (TAP5-1817) Stack frames in the ExceptionReport
should have a fly-over window showing source code, where available
Stack frames in the ExceptionReport should have a fly-over window showing source code, where available
------------------------------------------------------------------------------------------------------
Key: TAP5-1817
URL: https://issues.apache.org/jira/browse/TAP5-1817
Project: Tapestry 5
Issue Type: New Feature
Components: tapestry-core
Affects Versions: 5.4
Reporter: Howard M. Lewis Ship
Priority: Minor
This would be very cool, move the mouse over the stack frame, have a popup window display an extract from the source (much like templates are displayed).
This requires that Tapestry be able to find the Java source. I'd say look in two places:
1) On the classpath
2) Under "src/main/java" in the current working directory (with the relative path configurable via a symbol).
--
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
[jira] [Issue Comment Edited] (TAP5-1817) Stack frames in the
ExceptionReport should have a fly-over window showing source code, where
available
Posted by "Lance (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187669#comment-13187669 ]
Lance edited comment on TAP5-1817 at 1/17/12 1:28 PM:
------------------------------------------------------
Cool idea but in a multi-module build, there are likely many src/main/java folders. Also, there are likely to be projects that do not have the standard maven folder structure (I'm pointing the finger at YOU ant!)
Perhaps supporting two symbols would be better:
MAVEN_ROOTS: comma separated list of folders, recursively traverse each to include all src/main/java folders
SOURCE_ROOTS: comma separated list of arbitrary source roots (no traversal required)
was (Author: uklance):
Cool idea but in a multi-module build, there are likely many src/main/java folders. Also, there are likely to be projects that do not have the standard maven folder structure (I'm pointing the finger at YOU ant!)
Perhaps supporting two symbols would be better:
MAVEN_SOURCE_ROOTS: comma separated list of source roots, recursively traverse each to include all src/main/java folders
SOURCE_ROOTS: comma separated list of arbitrary source roots (no traversal required)
> Stack frames in the ExceptionReport should have a fly-over window showing source code, where available
> ------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1817
> URL: https://issues.apache.org/jira/browse/TAP5-1817
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Labels: exception-reporting
>
> This would be very cool, move the mouse over the stack frame, have a popup window display an extract from the source (much like templates are displayed).
> This requires that Tapestry be able to find the Java source. I'd say look in two places:
> 1) On the classpath
> 2) Under "src/main/java" in the current working directory (with the relative path configurable via a symbol).
--
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
[jira] [Commented] (TAP5-1817) Stack frames in the ExceptionReport
should have a fly-over window showing source code, where available
Posted by "Lance (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187669#comment-13187669 ]
Lance commented on TAP5-1817:
-----------------------------
Cool idea but in a multi-module build, there are likely many src/main/java folders. Also, there are likely to be projects that do not have the standard maven folder structure (I'm pointing the finger at YOU ant!)
Perhaps supporting two symbols would be better:
MAVEN_SOURCE_ROOTS: comma separated list of source roots, recursively traverse each to include all src/main/java folders
SOURCE_ROOTS: comma separated list of arbitrary source roots (no traversal required)
> Stack frames in the ExceptionReport should have a fly-over window showing source code, where available
> ------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1817
> URL: https://issues.apache.org/jira/browse/TAP5-1817
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Labels: exception-reporting
>
> This would be very cool, move the mouse over the stack frame, have a popup window display an extract from the source (much like templates are displayed).
> This requires that Tapestry be able to find the Java source. I'd say look in two places:
> 1) On the classpath
> 2) Under "src/main/java" in the current working directory (with the relative path configurable via a symbol).
--
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
[jira] [Commented] (TAP5-1817) Stack frames in the ExceptionReport
should have a fly-over window showing source code, where available
Posted by "Lance (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187669#comment-13187669 ]
Lance commented on TAP5-1817:
-----------------------------
Cool idea but in a multi-module build, there are likely many src/main/java folders. Also, there are likely to be projects that do not have the standard maven folder structure (I'm pointing the finger at YOU ant!)
Perhaps supporting two symbols would be better:
MAVEN_SOURCE_ROOTS: comma separated list of source roots, recursively traverse each to include all src/main/java folders
SOURCE_ROOTS: comma separated list of arbitrary source roots (no traversal required)
> Stack frames in the ExceptionReport should have a fly-over window showing source code, where available
> ------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1817
> URL: https://issues.apache.org/jira/browse/TAP5-1817
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Labels: exception-reporting
>
> This would be very cool, move the mouse over the stack frame, have a popup window display an extract from the source (much like templates are displayed).
> This requires that Tapestry be able to find the Java source. I'd say look in two places:
> 1) On the classpath
> 2) Under "src/main/java" in the current working directory (with the relative path configurable via a symbol).
--
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
[jira] [Issue Comment Edited] (TAP5-1817) Stack frames in the
ExceptionReport should have a fly-over window showing source code, where
available
Posted by "Lance (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187669#comment-13187669 ]
Lance edited comment on TAP5-1817 at 1/17/12 1:28 PM:
------------------------------------------------------
Cool idea but in a multi-module build, there are likely many src/main/java folders. Also, there are likely to be projects that do not have the standard maven folder structure (I'm pointing the finger at YOU ant!)
Perhaps supporting two symbols would be better:
MAVEN_ROOTS: comma separated list of folders, recursively traverse each to include all src/main/java folders
SOURCE_ROOTS: comma separated list of arbitrary source roots (no traversal required)
was (Author: uklance):
Cool idea but in a multi-module build, there are likely many src/main/java folders. Also, there are likely to be projects that do not have the standard maven folder structure (I'm pointing the finger at YOU ant!)
Perhaps supporting two symbols would be better:
MAVEN_SOURCE_ROOTS: comma separated list of source roots, recursively traverse each to include all src/main/java folders
SOURCE_ROOTS: comma separated list of arbitrary source roots (no traversal required)
> Stack frames in the ExceptionReport should have a fly-over window showing source code, where available
> ------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1817
> URL: https://issues.apache.org/jira/browse/TAP5-1817
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Labels: exception-reporting
>
> This would be very cool, move the mouse over the stack frame, have a popup window display an extract from the source (much like templates are displayed).
> This requires that Tapestry be able to find the Java source. I'd say look in two places:
> 1) On the classpath
> 2) Under "src/main/java" in the current working directory (with the relative path configurable via a symbol).
--
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