[
https://hibernate.onjira.com/browse/HV-578?page=com.atlassian.jira.plugin...
]
Hardy Ferentschik commented on HV-578:
--------------------------------------
{quote}
One thing I stumbled upon are several remaining references to slf4j. I think they could
all be removed, right? I'd add directly log4j as dependency to those projects which
have a log4j.properties for testing purposes.
{quote}
Right, technically there is no need for slf4j longer. If I remember right using slf4j was
not just about being able to use other loggers underneath, but there was also another
technical reason which evades me ATM. I am not sure whether this reason would still be
valid now. I am fine though with removing slf4j.
It might be worth to write a couple of sentences about logging in the documentation. That
we are using JBoss logging and that you still need to add an actual logger framework,
unless you are using Java logging in which case you need a logging.properties.
I think we should add this for the final release.
Remove remaining references to slf4j
------------------------------------
Key: HV-578
URL:
https://hibernate.onjira.com/browse/HV-578
Project: Hibernate Validator
Issue Type: Task
Components: documentation, engine
Affects Versions: 4.3.0.Beta1
Reporter: Gunnar Morling
Assignee: Gunnar Morling
Fix For: 4.3.0.CR1
With HV-481 we migrated to the JBoss Logging API. There are still some references to
slf4j which should be removed now.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira