[
https://issues.apache.org/jira/browse/VELOCITY-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637544#action_12637544 ]
Nathan Bubna commented on VELOCITY-621:
---------------------------------------
This error has been fixed since 1.6-beta1 was released. What happens if you use a more recent build from the trunk? If you don't want to check it out and build it yourself, i put one up here:
http://people.apache.org/~nbubna/velocity/engine/1.6-dev/> Update to SLF4J or workaround?
> ------------------------------
>
> Key: VELOCITY-621
> URL:
https://issues.apache.org/jira/browse/VELOCITY-621> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.4, 1.5
> Reporter: SebastianWagner
>
> I know that it has been discussed one year ago in VELOCITY-392
> but there is need for at least a workaround for people who are forced to use slf4j.
> For example other frameworks did already switch like Hibernate.
> So there is now definitely need for something to enable Velocity to run without errors in a environment with log4j-over-slf4j.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
