Re: [tinyTiM-discuss] Issue: Logging

[Markus U. <mar...@gm...>]

Hi,

2008/6/28 Lars Heuer <he...@se...>:

> Right, or we use Utilities like OneJar (not sure if that works since
> we need the API and an implementation of SLF4J).


Thanks, I never heard of One-JAR before :)
While it seems more sane than repackaging (sic!) all classes from multiple
JARs (we used to deploy a _huge_ "3rdparty.jar" at work, shudder), however,
I wouldn't do that _per default_. The more "modules"/"engines" you combine,
the higher the possibility that you end up with multiple versions of the
same archive (e.g., log4j). While this may not always be a problem,
sometimes you _need_ to update--and in this situation, it is less obvious
that a certain version of the library in question is contained here or
there. (Of course, you documented it and remembered to use find/grep/...
just to be sure, but there's always Murphy's Law :))

Therefore, I'd suggest that the possibility to use One-JAR is documented in
a README file if somebody really wants to deploy a single JAR, but it's not
used as part of the build process.
(Also, I didn't look whether this approach can be used repeatedly, i.e., if
one would combine tinyTiM with other libraries needed by the main
application.)

Hmmm... maybe we stick with the java.logging for the 1.5 series and wait for
> other opinions and may switch to SLF4J in the 2.0 branch (if TMAPI 2.0
> become reality).
>

Eh... you really want to wait THAT LONG? (Sorry, just kidding >:))
I could live with that, too, of course--though I'd still say it's better to
propagate good libraries/facades early as long as they're rather
lightweight  ;)

Ad astra, Markus