You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Antonio Petrelli (JIRA)" <de...@velocity.apache.org> on 2010/12/07 16:31:10 UTC
[jira] Assigned: (VELOCITY-621) Update to SLF4J or workaround?
[ https://issues.apache.org/jira/browse/VELOCITY-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli reassigned VELOCITY-621:
-----------------------------------------
Assignee: Antonio Petrelli
> 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
> Assignee: Antonio Petrelli
>
> 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@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org