What steps will reproduce the problem?

1. Create an Android application using the log4j logging as you described in the documentation in the Using log4j directly section.
2. Run the application on the phone in debug mode and the logging is working.
3. Export the Android application using Proguard and it gives unresolvable warnings about the log4j classes (I presume that's because they are simple Java classes and not "Android Java" classes).

Any suggestions?

Thanks. Daniel

If it doesn't work with Proguard, Is there any work-around to make it work? I am planning to use, but if it doesn't work with proguard, then I will be stuck. Any suggestions?

I'm very sorry for not having time to care for it yet.

In the meantime you can try to find some ProGuard config options fixing the problem. See http://proguard.sourceforge.net/index.html#manual/usage.html.

In the first week of april I will have time to fix it if it is possible or at least update the documentation.

Sorry for any inconvenience.

Can you please attach the exact warning/error message(s) of ProGuard?

You also can try to contact ProgGuard community. That is waht I will do in april if can't fix it.

Were you guys able to make it work? Tried all option that I can think of but doesn't seems to work.

has this been fixed?

Hi, Has this been fixed? Need something for proguard.

No, it has not been fixed, yet. Unfortunately, this project is not actively developed anymore due to lack of contributors.

Is there a work around?

I do not know, sorry.

Oooh! :( Thanks for the prompt replies! :)