<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hello all -</div><div><br>I did get slf4j-android working after going through the list here by grabbing the source code and patching it myself but I'm wondering if progress has been made on the issues below so that I can adopt a more official release?<br><br>Thanks in advance,<br>-Darrin<br><br><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I've run into a couple frustrating issues with slf4j-android<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">that you're no doubt aware of as it seems that some work has occurred<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">here: <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">1) <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=173">http://bugzilla.slf4j.org/show_bug.cgi?id=173</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Given that I'm dealing with a cross-platform library with lots of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">existing code the '23 character' android limit is a showstopper for<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">me. I cannot change all the library code to use 'simplename' for<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">example. Granted I see this as really an issue with Android - but<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">still we should be able to handle this in the android port. This<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">means that I cannot just handle it in the android specific portions<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">of the code - the already written libraries have to properly deal<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">with this issue by cropping the name of the logger - so that the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">library functions don't throw exceptions. This to me means that I<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">need to change the StaticLoggerBinder to instantiate a version of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">code that knows how to deal with this issue properly even when the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">client code isn't aware of it. Wendel's solution in the above thread<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">seems a reasonable solution. <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">2) Availability of android source-code from repo.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Given that this is an for me issue I'd like to put the fix in that wendell<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">suggest... use as much of the useful name as possible and hopefully<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Android comes around and fixes this limitation someday. I grabbed<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the codebase from git and I couldn't find references to the android<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">branch. Specifically it seems like wendell's fix is a decent<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">work-around for the android limitation. Unfortunately I cannot<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">easily do this and contribute any branches back to the open source<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">community because I cannot seem to find android code in this branch. Now<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">this said - I did find the slf4j-android code base on the website so I can move<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">forward... but why isn't this in Git?? <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">3) Really just a picky thing... slf4j-android does not appear to be<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">available from any publicly accessible maven repository. <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I've resolved this by adding the jar to my project and automatically<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">deploying it to the local repo - but this really isn't a very<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">elegant solution. Any chance the android version is going to be made<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">available anytime soon? I'd rather not package the jar as a build<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">artifact. <br></blockquote></blockquote></div><div><blockquote type="cite"><br></blockquote></div></body></html>