[
https://issues.apache.org/jira/browse/BVAL-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Vara resolved BVAL-60.
-----------------------------
Resolution: Fixed
Fix Version/s: 0.3-incubating
Yes, this one is complete. I decided against declaring jcl-over-slf4j as
optional, as it is really needed at runtime. The other option is to mix the
full jcl with slf4j, and if someone wants to do that, adding an exclude would
do the trick.
> Use SLF4J API for logging
> -------------------------
>
> Key: BVAL-60
> URL: https://issues.apache.org/jira/browse/BVAL-60
> Project: BeanValidation
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.1-incubating
> Reporter: Donald Woods
> Fix For: 0.3-incubating
>
>
> Suggested by David Jencks -
> Is anyone interested in using slf4j instead of commons-logging?
> If we use the slf4j-api, it would allow users to choose the logger, such as
> log4j, jul, simple, none, ....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
