[slf4j-user] SLF4J on the Google Android Platform

[Ceki Gulcu]

I think git supports Unix symbolic links but not all operating systems support 
sym links which makes sym-link in git pointless. I am not aware of a git 
equivalent for svn:externals.

However, you could modify the build file for the slf4j-android* module so that 
it copies the source files it needs from the slf4j-api module. This is pretty 
easy to do with an Ant target which you can then add to the Maven build life 
cycle.  By the way, initial versions of SLF4J where each binding also contained 
the contents of slf4j-api used to work exactly this way.

* feel free to suggest a better name.


Thorsten Möller wrote:
> On Thursday, October 22, 2009 4:46 PM [GMT+1=CET],
> Ceki Gulcu <ceki at 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
> 

-- 
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch