[
http://issues.ops4j.org/jira/browse/PAXLOGGING-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_10778
]
Niclas Hedhman commented on PAXLOGGING-10:
------------------------------------------
Ah! I understand. There is an additional legacy layer in between, which also
need to be accounted for.
Bear with me, I'll get this right.
> pax logging outputs wrong class and line number
> -----------------------------------------------
>
> Key: PAXLOGGING-10
> URL: http://issues.ops4j.org/jira/browse/PAXLOGGING-10
> Project: Pax Logging
> Issue Type: Bug
> Affects Versions: 0.9.5
> Reporter: Wouter de Vaal
> Assignee: Niclas Hedhman
> Priority: Minor
> Fix For: 0.9.6
>
>
> This is my favorite log4j appender:
> log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
> log4j.appender.stdout.layout.ConversionPattern=%d %p [%t][%C:%L] - %m%n
> I like to see the class and line number that does the logging ([%C:%L]), but
> with pax you get this:
> ...[org.ops4j.pax.logging.internal.PaxLoggerImpl:78]...
> So I don't get the originating logger class and lines in the output.
> slf4j is used within the code, which works fine with when using slf4j/log4j
> without pax-logging, so it seems to me this should be feasable for pax
> logging as well..
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
