Tracker issue for JBoss Modules portion of EAP62_2010 Logging Unification. ANDIAMO-7 compliance.
Still working on a viable solution.
Cannot be fixed for 6.2.
Hey David, can you provide some justification on why this will be deferred, (or will not be done at all?). Thanks.
It's a technical problem. Our i18n logging solution requires jboss-logging; jboss-logging is not available to jboss-modules because it is loaded *as* a module, so jboss-modules cannot link directly against it. JBoss Modules also has an internal logging API which is designed to accommodate the logging system initializing after the module system bootstraps; this API also constrains how the logging implementation can be implemented, so to change that somehow would break compatibility, which is a consideration for any proposed solution. So far I do not have a workable solution to this problem, so it cannot be fixed until a solution presents itself.
So, it's a chicken-egg problem, thanks.
Exactly. I have a couple ideas but I don't know if they're really workable, but I do know it can't be done by 6.2 in any case.