Wrong methodname and linenumber in combination with java.util.logging
---------------------------------------------------------------------
Key: PAXLOGGING-32
URL: http://issues.ops4j.org/jira/browse/PAXLOGGING-32
Project: Pax Logging
Issue Type: Bug
Affects Versions: 1.1.1
Environment: Windows XP with Java 1.5 and Equinox as OSGI platform
Reporter: Florian
Assignee: Niclas Hedhman
Using a conversion-pattern for log4j like this
log4j.appender.stdout.layout.ConversionPattern=%d{HH:mm:ss} %-5p [%-35c{1} -
%-25M:%-4L] - %m%n
and the standard logging framework for java "java.util.logging" the parameter
"M" for methodname and "L" for linenumber are not correctly resolved. It seems
that the classes are resolved one step too high in the stacktrace.
This effect is the same whe using the (upper-case) "C" parameter for resolving
full qualified class names. Lower-case "c" parameter is resolved correctly.
I've attached a test bundle which demonstrates this behaviour and also outputs
the expected results. However, for my experience, every bundle using
java.util.logging struggles upon this problem.
--
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
