Ah OK fair call.
It's another change of behaviour from upgrading from 5.3 to 5.4 I noticed
- 5.3 came with log4j-slf4j stuff included.
5.4 comes with plug-your-own.
Closed/Won't Fix the JIRA I created jumping the gun.
https://issues.apache.org/jira/browse/TAP5-2393
Sorry for poking my nose in devs.
Thanks for response Kalle.
On Thu, 02 Oct 2014 01:05:54 +1000, Kalle Korhonen
<kalle.o.korho...@gmail.com> wrote:
On Wed, Oct 1, 2014 at 7:49 AM, Chris Mylonas <ch...@opencsta.org> wrote:
Hi - the logs on 5.4 didn't seem to be displaying the text logo from 5.3
or what services are REAL/VIRTUAL/etc.
Just plain old standard pom.xml from quickstart for 5.3.7 used, then
changed version to 5.4-beta-22
I was previously getting until adding logback-classic
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
further
details.
[INFO] Started SelectChannelConnector@0.0.0.0:8080
Should some sort of logging framework be included in the default
tapestry
pom? (jira ticket for inclusion?)
No, absolutely not. This works as designed with a fairly obvious message.
SLF allows you, as the application developer, to plug in whatever logging
framework you want (jdk logging, log4j, logback, you-name-it-logger
etc.).
Kalle
--
Using Opera's mail client: http://www.opera.com/mail/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
