[
https://issues.apache.org/jira/browse/LOG4J2-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070192#comment-14070192
]
Gary Gregory edited comment on LOG4J2-728 at 7/22/14 12:24 PM:
---------------------------------------------------------------
If you are now developing a Log4j plugin, you must also create a .dat file for
all your plugin metadata with our annotation processor and have Log4j find it
at runtime. I am not sure this is documented on the site :-(
When I see messages like:
{noformat}
ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position
16 in conversion pattern.
{noformat}
it usually means that some plugin metadata is not found.
was (Author: garydgregory):
If you are now developing a Log4j plugin, you must also create a .dat file for
all your plugin metadata with our annotation processor and have Log4j find it
at runtime. I am not sure this is documented on the site :-(
> Look for log4j2.xml in assets folder (or the application data) in an Android
> APK.
> ---------------------------------------------------------------------------------
>
> Key: LOG4J2-728
> URL: https://issues.apache.org/jira/browse/LOG4J2-728
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.0-rc2
> Environment: Android
> Reporter: Nelson MELINA
> Labels: android
>
> To add files in an Android apk, you need to put them in an assets folder and
> then they are in an "assets" folder in the APK.
> Log4j 2 needs to find it there when it exists (not the case now).
> Also would it be possible to load the xml configuration file from the
> application data (
> https://developer.android.com/guide/topics/data/data-storage.html ) ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
