Ceki - That's not a stupid question. It is a 'regular jar' and is assembled in the usual way (no special maven plugins used that would call anything other than javac) however you'd not be able to use it in an executable without a provided 'android.jar'. This likely means this will never be used in a 'regular java app' but rather only on the android platform. That said this is really no different than the other platforms that you support in that sense since they too are dependent upon other logging systems being in place on the target platform. As with any other jar all I did to add it to my android project was to install it into the repo (local repo) and then to include it as a dependency in my pom file. So what you'll want to put out there are the generated ".jar", "source.jar" and generated poms. -Darrin On Aug 24, 2010, at 4:33 PM, Ceki Gülcü wrote:
On 24/08/2010 3:43 PM, Thorsten Möller wrote:
@Ceki: What would be required in order to publish the artifacts to Maven central - I never did this.
The simplest way to publish the slf4j-android artifacts on the maven central repo would be for you to point me to a location where these are available. All files placed in your local repository when you build and install the org.slf4j:slf4j-android artifact are required (not just the slf4j-android.jar file). Zipping them and sending these files in an email is also OK. Once I get my hand on the files, I can publish them on the central repo.
BTW, is the generated jar file, namely slf4j-android.jar, really a jar file loadable on a regular JVM? My apologies if it's a stupid question.
-- Ceki _______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch http://qos.ch/mailman/listinfo/slf4j-dev