[
https://issues.apache.org/jira/browse/TAP5-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789041#action_12789041
]
Howard M. Lewis Ship edited comment on TAP5-916 at 12/11/09 7:14 PM:
---------------------------------------------------------------------
This does come down to a question of what's good for users savvy enough to use
Logback, vs. what works best for general users (who use Log4J out of habit and
never think about logging beyond that).
was (Author: hlship):
This does come down to a queston of what's good for user's savvy enough to
use Logback vs. general users who use Log4J out of habit.
> Tapestry projects include logging impls as compile depencency
> -------------------------------------------------------------
>
> Key: TAP5-916
> URL: https://issues.apache.org/jira/browse/TAP5-916
> Project: Tapestry 5
> Issue Type: Bug
> Reporter: Ben Tomasini
> Priority: Minor
>
> When including tapestry-ioc in my projects, my maven dependencies look like
> this:
> <dependency>
> <groupId>org.apache.tapestry</groupId>
> <artifactId>tapestry-ioc</artifactId>
> <version>5.1.0.5</version>
> <exclusions>
> <exclusion>
> <artifactId>slf4j-log4j12</artifactId>
> <groupId>org.slf4j</groupId>
> </exclusion>
> <exclusion>
> <artifactId>log4j</artifactId>
> <groupId>log4j</groupId>
> </exclusion>
> </exclusions>
> </dependency>
> I am using logback in my application and need the exclude log4j. Ideally,
> these dependencies should be changed to <scope>provided</scope> in the
> tapestry poms.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
