Thorbjoern Ravn Andersen wrote:
c...@slf4j.org skrev:
Fewer eclipse warnings
Would it be a reasonable goal that the code base compile without any
Eclipse warnings at all?
Reasonable yes, possible no. There are 5 warnings total in the project
(all modules). Two in LoggerFactory about
As in revision 1325, the mention of logback is quiet discreet. I will not bend
backwards and avoid mentioning logback just to prove that SLF4J provides a
neutral playing field. I do not wish to start a debate about morality.
BTW, have you actually looked at 1325?
Thorbjoern Ravn Andersen
You can easily make maveninzed project eclipse-ready by launching the mvn
eclipse:eclipse command. Once you do that, you just import into Eclipse the
various SLF4J modules as eclipse projects. Once you have eclipse and maven
installed, and SLF4J checked out, the mvn eclipse:eclipse procedure
Thorbjoern Ravn Andersen wrote:
I humbly disagree, and deserves credit for that feels more like
boasting than providing neutral information (as you happen to have
written both pieces of software AND the manual providing the link).
Deserves credit is the term I used in an email. It is not
Ceki Gulcu skrev:
As in revision 1325, the mention of logback is quiet discreet. I will
not bend backwards and avoid mentioning logback just to prove that
SLF4J provides a neutral playing field. I do not wish to start a
debate about morality.
BTW, have you actually looked at 1325?
I read
