[slf4j-user] SLF4J on the Google Android Platform

[Thorsten Möller]

On Friday, October 23, 2009 3:17 PM [GMT+1=CET],
Ceki Gulcu <ceki at qos.ch> wrote (with possible deletions):

>>>> Note that you need to install the Android SDK and set an
>>>> environment variable ANDROID_SDK_HOME in order to build it.
>>> Why on earth isn't it possible to fetch android jar from the central
>>> Maven repo or any other repo? Isn't Android licensed under Apache?
>
>> Probably because Google guys don't care much about Maven... Joking
>> apart, other options would be to install android.jar to the local
>> Maven repos, or to use toolchains [1]. Unfortunately, all of them
>> require some initial setup of the environment; the latter is even
>> not officially released yet.
>
> Adding a manual installation step would be a regression compared to
> the current
> build.
I fully agree.


> However, we could imagine that while optional for an anonymous
> build,
> building for a release would require slf4j-android to be build and
> packaged
> inside SLF4J. (Here I am assuming slf4j-android is shipping with
> SLF4J proper.)
This solution would be neat. However, there is yet another issue that 
currently prevents it, which is the fact that slf4j-android can not 
inherit from the SLF4J root POM. The reason is that android.jar contains 
a tailored JUnit version (basically without the SWING GUI because SWING 
does not exist on the android platform) which needs to be used. In order 
to inherit from the root pom it would be required not to inherit the 
JUnit dependency. Unfortunately, there is no possibility in Maven to 
exclude a dependency inherited from a parent project.


> Alternatively, you could host slf4j-android elsewhere or host it at
> slf4j.org
> but as a separate project(sub-project).
I would prefer the latter, i.e., host it as a kind of sub project at 
slf4j.org to have everything in one place.


> Whenever you are ready to
> make a release
> you would just copy the contents of slf4j-android project into
> http://slf4j.org
> without any intervention on my part. I would obviously prefer the
> latter approach.
That would be also my preference. The current version would then be 
created from SLF 1.5.8 and I would prefer to keep the version numbers in 
sync.

The question to me now is how-to proceed. What do you need next to get 
it online.

Best,
Thorsten