In a stack trace, any lines associated with line #1 of a class are likely to be 
synthetic methods as should be "uninteresting"
------------------------------------------------------------------------------------------------------------------------------

                 Key: TAP5-859
                 URL: https://issues.apache.org/jira/browse/TAP5-859
             Project: Tapestry 5
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.2.0.0
            Reporter: Howard M. Lewis Ship
            Priority: Minor


# 
collective.t5.pages.widendev.InitializationTesting.resetIncrementCount(InitializationTesting.java:20)
# 
collective.t5.pages.widendev.InitializationTesting.pageDidInitialize(InitializationTesting.java)
# 
collective.t5.lifecycle.WLifecycleTrackerImpl$1.operateOn(WLifecycleTrackerImpl.java:45)
# 
collective.t5.lifecycle.WLifecycleTrackerImpl$1.operateOn(WLifecycleTrackerImpl.java:1)
 

You see that pattern a lot: line 1, then a real line number, when associated 
with inner classes.


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

Reply via email to