tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Closed: (TAP5-393) Tapestry IOC should log the names of any loaded module classes and clearly indicate module classes that could not be loaded
Date Mon, 01 Dec 2008 18:51:45 GMT

     [ https://issues.apache.org/jira/browse/TAP5-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

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

       Resolution: Fixed
    Fix Version/s: 5.1.0.0

Logs each loaded class on logger org.apache.tapestry5.ioc.RegistryBuilder at level info.

> Tapestry IOC should log the names of any loaded module classes and clearly indicate module
classes that could not be loaded
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-393
>                 URL: https://issues.apache.org/jira/browse/TAP5-393
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.1.0.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.1.0.0
>
>
> If you screw up the manifest of a module or have other classpath problems, it is impossible
to know exactly what modules have been loaded.  Logging that (perhaps using the org.apache.tapestry5.ioc.Registry
logger) would be a big help.

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


Mime
View raw message