noveogroup/android-logger

Useful logger for Android based on standard android.util.Log class. Simple lightweight (< 50 Kb) implementation of SLF4J API. Easy but powerful configuration via properties file and some additional helpful logging methods. Easy analogue of popular log4j library.

android-logger's Issues

Configuration API

tag from classname

In logback-android, the 'tag' comes from the name of the class passed to Logger.getLogger. However, in android-logger the 'tag' has to be hard-coded in android-logger.properties.

There should be a way to specify that we want to use the classname as the tag.

Check android-logger is thread-safe

Means more than just thread-safe synchronization: it should print logs without "mixing".

Deploy to Maven Central

• update Getting Started

Patterns with {sign count} does not work

Using Gradle dependency 'com.noveogroup.android:android-logger:1.3.1'

Into android-logger.properties

root=DEBUG:Euro01:%C gives "D/Euro01: com.example.olivier.euro01.CoinActivity6Fragment.trace2(CoinActivity6Fragment.java:74) onCreate"
Seems ok (but is it normal that source is output ?)

root=DEBUG:Euro01:%C{2} gives "D/Euro01: com.example onCreate"
root=DEBUG:Euro01:%C{3} gives "D/Euro01: com.example.olivier onCreate"
root=DEBUG:Euro01:%caller{3} gives "D/Euro01: com.example.olivier onCreate"
Seems ok

root=DEBUG:Euro01:%caller{-3} gives "D/Euro01: com.example.olivier.euro01.CoinActivity6Fragment.trace2(CoinActivity6Fragment.java:74){-3} onCreate"
root=DEBUG:Euro01:%caller{+3} gives "D/Euro01: com.example.olivier.euro01.CoinActivity6Fragment.trace2(CoinActivity6Fragment.java:74){+3} onCreate"
NOT ok, com.example.olivier not removed AND {-3} printed

Add isEnabled methods

• Log.isVerboseEnabled()
• Log.isDebugEnabled()
  ... etc ...

Parametrize logging statement in presence of a Throwable

like this: http://www.slf4j.org/faq.html#paramException

where to put the file android-logger.properties?

i put it in (src/main/resources/android-logger.properties):

and it always log out:
Logger configuration file is empty. Default configuration will be used

Rename the library

...

App crash due to format exception

Log.a("jsonResponse" + jsonResponse);

This caused the below crash:
java.util.MissingFormatArgumentException: Format specifier: 3a
at java.util.Formatter.getArgument(Formatter.java:1111)
at java.util.Formatter.doFormat(Formatter.java:1076)
at java.util.Formatter.format(Formatter.java:1042)
at java.util.Formatter.format(Formatter.java:1011)
at java.lang.String.format(String.java:1803)
at java.lang.String.format(String.java:1777)
at com.noveogroup.android.log.PatternHandler.print(PatternHandler.java:355)
at com.noveogroup.android.log.SimpleLogger.print(SimpleLogger.java:63)
at com.noveogroup.android.log.AbstractLogger.a(AbstractLogger.java:167)
at com.noveogroup.android.log.Log.a(Log.java:313)
at com.myapp.APIController$13.onResponse(ChatController.java:696)
at com.squareup.okhttp.Call$AsyncCall.execute(Call.java:170)
at com.squareup.okhttp.internal.NamedRunnable.run(NamedRunnable.java:33)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)

Is this a known bug? I'm running latest version.

configuration in manifest, resources, assets, etc. ???

Implement all TODOs

... just to remember it

Duplicate entry for slf4j class - StaticLoggerBinder

Our release build fails with the following error

Warning:Exception while processing task java.io.IOException: Can't write  
    [.../app/build/intermediates/transforms/proguard/release/jars/3/1f/main.ja] 
    (Can't read [.../.gradle/caches/modules-2/files 
2.1/com.noveogroup.android/android-
logger/1.3.6/5cb3345e23efd3d3a195eb8c4ae5b627189f8159/android-logger-
1.3.6.jar(;;;;;;**.class)] (Duplicate zip entry [org/b/c/a.class == 
android-logger-1.3.6.jar:org/slf4j/impl/StaticLoggerBinder.class]))

Looks like the internal slf4j package conflicts with other libraries depending on the slf4j library

Logging into file

Implement some simple version of http://logback.qos.ch/manual/appenders.html#RollingFileAppender

Add section about LOGBack to readme

Write short description of LOGBack, add a link, compare loggers, etc.

Feature: Dynamic tags

Can the tag be "dynamically" set? Maybe something like:

Properties:

# All classes in the following package will use the String or class as the logging tag
logger.com.example.activity=DEBUG:*

Code:

// TAG = MainActivity
private static final Logger LOG = LoggerManager.getLogger(MainActivity.class);

// TAG = "@@@@@@@"
private static final Logger LOG = LoggerManager.getLogger("@@@@@@@");

This would make the library extremely more useable for larger projects without defining different tags for packages or if you need to target certain classes quickly.

add special constant or class to access to debug logger with name "XXX" or something similar ...

Formatting log output

1. Implement com.noveogroup.android.log.PatternHandler.
2. Implement PatternHandlerTest.
3. Delete old code from com.noveogroup.android.log.Utils and UtilsTest.

Cannot log content with "%" symbol.

This is using the 1.3.2 release.

Logging a message through SLF4J with a % symbol, either in the format string or argument string, results in an exception.

log.trace("This will throw {}", "Happens 100%!");

Partial stack trace:

     Caused by: java.util.MissingFormatArgumentException: Format specifier: ;
            at java.util.Formatter.getArgument(Formatter.java:1111)
            at java.util.Formatter.doFormat(Formatter.java:1076)
            at java.util.Formatter.format(Formatter.java:1042)
            at java.util.Formatter.format(Formatter.java:1011)
            at java.lang.String.format(String.java:1999)
            at java.lang.String.format(String.java:1973)
            at com.noveogroup.android.log.PatternHandler.print(PatternHandler.java:298)
            at com.noveogroup.android.log.SimpleLogger.print(SimpleLogger.java:56)
            at org.slf4j.impl.AndroidLoggerAdapter.log(AndroidLoggerAdapter.java:63)
            at org.slf4j.impl.AndroidLoggerAdapter.trace(AndroidLoggerAdapter.java:91)

Stack trace ignored

In AndroidLoggerAdapter.java line 100

public void trace(String msg, Throwable t) {
        log(Logger.Level.VERBOSE, msg);
}

All other log levels (all but one) has the same bug.

Can you share some screenshots of the app ui, like for the main screen

%caller and %source do not work properly with slf4j

When using the SLF4J bindings, both %caller and %source always results in AndroidLoggerAdapter as the caller/source instead of the actual class that the SLF4J log call was done in.

#android-logger.properties file
logger.com.example=DEBUG:Example:[%t] %caller{-3.-15}%source

//SLF4J test
private static final Logger log = LoggerFactory.getLogger(MainActivity.class);

public void doTest() {
    log.info("Testing");
}

05-19 09:23:45.129 736-804/com.example.activity D/Syncronous: [main] AndroidLoggerAdapter#log:55(AndroidLoggerAdapter.java:55) Testing

properties file location

Hi,

We've tried putting the android-logger.properties file in the src folder and a lot others, but we always get the "Logger configuration file is empty. Default configuration will be used" message. Would you have any other suggestions?

We are using gradle and Android Studio if that helps.

Thank you.

try Gradle build configuration

Can save log file?

if i want to save log file in android ,Can do it?

Implement an easy way to switch to LOGBack

This library is "little LOGBack". So it should implement some easy way to switch without a lot of configurations and so on.

For example:
User log messages via our classes and can set some flag to true and start using LOGBack via our classes.

Logger throws exception if API level <= 8

While initializing Logger on device with API Level 8 I get following exception:

04-17 11:25:33.598: ERROR/AndroidRuntime(336): FATAL EXCEPTION: main
java.lang.ExceptionInInitializerError
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1429)
at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2577)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679)
at android.app.ActivityThread.access$2300(ActivityThread.java:125)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ExceptionInInitializerError
at com.noveogroup.android.MainActivity.(MainActivity.java:28)
... 15 more
Caused by: java.lang.NoSuchMethodError: java.util.Properties.stringPropertyNames
at com.noveogroup.android.log.LoggerManager.loadConfiguration(LoggerManager.java:121)
at com.noveogroup.android.log.LoggerManager.(LoggerManager.java:143)
... 16 more

for this line:

private static final Logger logger = LoggerManager.getLogger();

How to disable the log level

Hi, i want to disable all logging levels including VERBOSE, DEBUG, INFO, WARN, ERROR, ASSERT in the release version. How can i configure it in the android_properties file. Thanks

fast switch between debug and release logger configurations

There is an exception

There is an exception when i call

 logger.d("80%");

java.util.UnknownFormatConversionException

Do some PR after new version of library will be impelemnted

• http://www.theultimateandroidlibrary.com/
• http://habrahabr.ru/post/116376/
• http://androidweekly.net/

Improve configuration

1. Implement configuration changes (see them below).
2. Implement formatting (#1).
3. Write special section in README about formatting.
4. Update section "configuration" in README.
5. Update samples.
6. Test changes.
7. Release new version

New configuration principals:

1. There is a logger's hierarchy which is like package hierarchy.
2. On each its level we can place filter or printer or both.
3. Filter - filter log messages, thank you cap.
4. Printer - prints messages.
5. Messages are printed only once (todo discuss).
6. Printers are configured with format string for tag and messages.