On Thursday, October 22, 2009 4:46 PM [GMT+1=CET], Ceki Gulcu <c...@qos.ch> wrote (with possible deletions):
> Sounds great. The easiest approach to integrate your contributions > would be to fork slf4j on github and let us know when you are done so > that we can study the results. Ok, I'll try. Good chance to start working with Git ;-) > To fork SLF4J, create a user id on github and then go to > http://github.com/ceki/slf4j and click on fork. You should then > locally clone your fork and publish the results into the forked > version. I can already tell you that I needed to merge the SLf4J-API project and the new binding implementation into one (Maven) project. The reason is rather complicated to explain. In short, it is due to the fact that SLF4J API removes the dummy impl.* classes during the build from the target Jar, which is not compatible with the Android Dexer. If Git supports something like symbolic links for files and directories it could be "cleanly" integrated, otherwise, the code of the API part needs to be duplicated. Do you know if Git supports symbolic links, or something equivalent to svn:externals? -- Thorsten _______________________________________________ user mailing list user@slf4j.org http://www.slf4j.org/mailman/listinfo/user
