tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1519) Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker
Date Tue, 03 May 2011 23:42:03 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028508#comment-13028508
] 

Hudson commented on TAP5-1519:
------------------------------

Integrated in tapestry-trunk-freestyle #336 (See [https://builds.apache.org/hudson/job/tapestry-trunk-freestyle/336/])
    TAP5-1519: Ensure that all calls to invoke methods and constructors with dependencies
are tracked with the OperationTracker


> Ensure that all calls to invoke methods and constructors with dependencies are tracked
with the OperationTracker
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1519
>                 URL: https://issues.apache.org/jira/browse/TAP5-1519
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3.0, 5.2.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3.0
>
>
> I've noticed that Tapestry is not always great about tracking what method or constructor
is being invoked, which can make it harder to track down injection problems (which are automatically
hard to start with).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message