On 12-11-11 6:52 PM, Olivier Lamy wrote:
If the discussion is now transitioning to users want flexible
logging and the choice of a logging framework that's fine. But I
still maintain the CLI use of logging can be limited and
constrained while allowing integrators to make the small changes
necessary to add flexible logging. But if we want to choose a
framework let's look at the options, if people want to go that
route, and select the best option.
Integrators ? Again what do you mean with that ? I don't understand
why the default Apache Maven couldn't be able to propose a default
advanced logging implementation. The size of the jars is around 500K
so frankly I don't see that as a blocking issue as we already
download internet:-). (and perso I'd like to test some ideas using
jansi for possible colorized logging) And I don't understand why we
must wait folks doing alternate distributions providing this
feature.
m2e uses logback and switching to another slf4j provider will be
extremely expansive if not impossible at this point. I believe
downstream m2e consumers like JBoss Tools and Spring Tool Suite are in
the same position. We already repackage Maven as part of m2e build, so
removing slf4j-simple or log4j will not a problem, at least as long as
Maven core functionality only uses slf4j and does not depend on
specific logging library.
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
