tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAP5-2035) Make it easier to choose another slf4j backend
Date Wed, 19 Dec 2012 07:57:15 GMT

     [ https://issues.apache.org/jira/browse/TAP5-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jochen Kemnade updated TAP5-2035:

    Attachment: 0001-Have-tapestry-ioc-depend-on-slf4j-api-instead-of-slf.patch

* Have tapestry-ioc depend on slf4j-api instead of slf4j-log4j
* Move dependency on slf4j-log4j12 to quickstart-generated project
* Update slf4j to 1.7.2

> 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
>              Labels: logging, patch
>         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

View raw message