[
http://issues.ops4j.org/browse/PAXLOGGING-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919#action_13919
]
Guillaume Nodet commented on PAXLOGGING-96:
-------------------------------------------
Moving the slf4j implementation to pax-logging-impl is not really possible as
the only interface between pax-logging-api and pax-logging-impl is the
pax-logger so that the service can be made dynamic while still allowing clients
to run. Not sure how to solve your problem cleanly.
> Plz dont bundle the sl4fj impl w/ pax-logging-api it causes classpath
> problems etc
> ----------------------------------------------------------------------------------
>
> Key: PAXLOGGING-96
> URL: http://issues.ops4j.org/browse/PAXLOGGING-96
> Project: Pax Logging
> Issue Type: Improvement
> Reporter: Miroslav Pokorny
>
> Firstly i love pax for its simplicity but its wrong imho to bundle an
> implementation w/ the api.jar because it is now problematic or a headache to
> override the impl. It also makes it difficult to mix regular java and pax
> tests simply because a class referring to a pax api now also pulls in the
> pax-logging bundled slf4j which means more headaches when there are two
> different incompatible slf4js. My hope would be that the two are separated.
> Im guessing w/ pax-logging 1.6.0 this problem is probably gone but if the two
> were separated then this problem should probably not repeat.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
