You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Kalle Korhonen (JIRA)" <ji...@apache.org> on 2013/01/17 21:12:13 UTC
[jira] [Resolved] (TAP5-2035) Make it easier to choose another
slf4j backend
[ https://issues.apache.org/jira/browse/TAP5-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kalle Korhonen resolved TAP5-2035.
----------------------------------
Resolution: Fixed
Fix Version/s: 5.4
Agreed. Patch applied, thanks! Not deemed critical enough for 5.3.x, use excludes.
> Make it easier to choose another slf4j backend
> ----------------------------------------------
>
> Key: TAP5-2035
> URL: https://issues.apache.org/jira/browse/TAP5-2035
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.3, 5.4
> Reporter: Jochen Kemnade
> Assignee: Kalle Korhonen
> Labels: logging, patch
> Fix For: 5.4
>
> Attachments: 0001-Have-tapestry-ioc-depend-on-slf4j-api-instead-of-slf.patch
>
>
> Tapestry-IOC includes slf4j-log4j12 and log4j as compile dependencies. This is not necessary and makes it hard for users to choose another logging backend for slf4j. Tapestry-IOC should depend on slf4j-api only and the backend should be exchangeable without having to exclude transitive dependencies.
> However, it seems sensible to provide log4j as the default binding for quickstart projects, so the dependency on slf4j-log4l12 should be added to the final project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira