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)" <ji...@apache.org> on 2008/12/04 22:26:44 UTC

[jira] Created: (TAP5-403) Test failures under jdk1.6

Test failures under jdk1.6
--------------------------

                 Key: TAP5-403
                 URL: https://issues.apache.org/jira/browse/TAP5-403
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-ioc
    Affects Versions: 5.1.0.0, 5.0.18
            Reporter: Andreas Andreou


The failures are due to an incorrect error message generated by org.apache.tapestry5.ioc.internal.util.OneShotLock

As mentioned in the comments of that method, Thread.currentThread().getStackTrace[4] is used instead of 
Thread.currentThread().getStackTrace[3] and this was found by trial and error... in java1.6 however, 
Thread.currentThread().getStackTrace[3] is indeed the correct choice for the caller method

-- 
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-403) OneShotLock tests fail under JDK 1.6 because of JVM differences

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

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

    Summary: OneShotLock tests fail under JDK 1.6 because of JVM differences  (was: Test failures under jdk1.6)

> OneShotLock tests fail under JDK 1.6 because of JVM differences
> ---------------------------------------------------------------
>
>                 Key: TAP5-403
>                 URL: https://issues.apache.org/jira/browse/TAP5-403
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.1.0.0, 5.0.18
>            Reporter: Andreas Andreou
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1.0.0
>
>
> The failures are due to an incorrect error message generated by org.apache.tapestry5.ioc.internal.util.OneShotLock
> As mentioned in the comments of that method, Thread.currentThread().getStackTrace[4] is used instead of 
> Thread.currentThread().getStackTrace[3] and this was found by trial and error... in java1.6 however, 
> Thread.currentThread().getStackTrace[3] is indeed the correct choice for the caller method

-- 
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: (TAP5-403) Test failures under jdk1.6

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

Howard M. Lewis Ship reassigned TAP5-403:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> Test failures under jdk1.6
> --------------------------
>
>                 Key: TAP5-403
>                 URL: https://issues.apache.org/jira/browse/TAP5-403
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.1.0.0, 5.0.18
>            Reporter: Andreas Andreou
>            Assignee: Howard M. Lewis Ship
>
> The failures are due to an incorrect error message generated by org.apache.tapestry5.ioc.internal.util.OneShotLock
> As mentioned in the comments of that method, Thread.currentThread().getStackTrace[4] is used instead of 
> Thread.currentThread().getStackTrace[3] and this was found by trial and error... in java1.6 however, 
> Thread.currentThread().getStackTrace[3] is indeed the correct choice for the caller method

-- 
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] Closed: (TAP5-403) OneShotLock tests fail under JDK 1.6 because of JVM differences

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

Howard M. Lewis Ship closed TAP5-403.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.1.0.0

> OneShotLock tests fail under JDK 1.6 because of JVM differences
> ---------------------------------------------------------------
>
>                 Key: TAP5-403
>                 URL: https://issues.apache.org/jira/browse/TAP5-403
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.1.0.0, 5.0.18
>            Reporter: Andreas Andreou
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1.0.0
>
>
> The failures are due to an incorrect error message generated by org.apache.tapestry5.ioc.internal.util.OneShotLock
> As mentioned in the comments of that method, Thread.currentThread().getStackTrace[4] is used instead of 
> Thread.currentThread().getStackTrace[3] and this was found by trial and error... in java1.6 however, 
> Thread.currentThread().getStackTrace[3] is indeed the correct choice for the caller method

-- 
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