[
http://jira.nuxeo.org/browse/WEB-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48228#action_48228
]
Florent Guillaume commented on WEB-155:
---------------------------------------
> I found it useful to print out both which ones were used and which ones were
> not used, so I knew if my changes to various files were having any effect
But this should logged with the rest of the DEBUG info already available during
startup.
> Similarly, it's good to know which directories are being used for various
> things, for example, "Where did my files get copied to?"
Same thing, DEBUG.
I don't see why a separate logger should be used. If you want to separate them
out easily, you can add a log4j.xml appender to a new file that only logs the
interesting classes for bundles.
> improve debugging capabilities for osgi bundles
> -----------------------------------------------
>
> Key: WEB-155
> URL: http://jira.nuxeo.org/browse/WEB-155
> Project: Nuxeo Web Engine
> Issue Type: Improvement
> Reporter: Ian Smith
> Assignee: Ian Smith
>
> The problem: When you are developing your own code based on nuxeo EP or
> webengine it is easy to make a mistake and then your code will mysteriously
> "disappear" from the system. This is because the OSGi bundle was considered
> invalid in some way.
> Solution: Add a debugging channel (log4j logger) that is only for this type
> of information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
