[logback-user] Substituting class/method names in logback log files with original names when deploying obfuscated code

Chris Pratt thechrispratt at gmail.com
Mon Nov 28 17:50:36 CET 2011

You do realize that if you supply the mapping file to the end user, there
is really no reason to obfuscale the code in the first place.  They'll have
everything they need to properly un-obfuscate and decompile it.
On Nov 28, 2011 7:32 AM, "Christopher BROWN" <brown at reflexe.fr> wrote:

> Hello,
> What would be the best way to handle logging with logback when deploying
> obfuscated code?
> For example, with YGuard, when the obfuscator runs, it outputs a mapping
> file of obfuscated code (class names, method names, etc) to unobfuscated
> code.  When a stacktrace or just any logging trace is output, the
> class/method names are obviously obfuscated.  As it's possible to deploy
> this mapping with the code, say embedded in the same ".jar", all the
> information I would need is available.
> Without too much re-writing of code (default formatting with logback),
> what would be the best way to dynamically replace matching class/method
> names?
> Thanks,
> Christopher
> _______________________________________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://mailman.qos.ch/mailman/listinfo/logback-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20111128/c87b6209/attachment-0001.html>

More information about the Logback-user mailing list