Ralph Goers skrev:
Yes, I knew that. The issue is I really don't want to us Eclipse as my
IDE. It seems silly to load it just to see the warnings. Most, if not
all, the ones you mentioned would also be shown in IntelliJ. Running
something as a maven report is far more palatable than being
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
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
On Apr 23, 2009, at 9:25 AM, 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?
Unfortunately, I use IntelliJ. Presumably SLF4J could just use the
checkstyle plugin
Ralph Goers skrev:
Unfortunately, I use IntelliJ. Presumably SLF4J could just use the
checkstyle plugin and then I could verify it before committing.
Setting up checkstyle for a multi module project is a bit tricky, but
I've
I don't mind a few extra commits.
If you can use Eclipse on
