:) I'm also moving to gradle so it's a different kind of magic.
compile("org.apache.tapestry:tapestry-core:$tapestryVersion") {
exclude module: 'slf4j-log4j12'
exclude module: 'log4j'
}
Making it a compile dependency saves end users from needing to include log4j
in their poms (or other dependency managers), but it feels... smelly? There
isn't actually a compile dependency, right?
Josh
On Tue, Jan 18, 2011 at 8:54 AM, Howard Lewis Ship <[email protected]> wrote:
> Yes, but the vast majority will use Log4J, and those enlightened
> enough to prefer Logback will also be enlightened enough to know the
> Maven pom incantation to include logback and exclude log4j.
>
> On Tue, Jan 18, 2011 at 7:52 AM, Josh Canfield <[email protected]>
> wrote:
> > Agreed. I'm moving to logback and have to exclude log4j.
> > On Jan 18, 2011 7:32 AM, "Massimo Lusetti" <[email protected]> wrote:
> >> Why there's a log4j dep? ... Maybe I'm in the 0.00001% of applications
> >> (who) will need to override this dependency to not use Log4J but why
> >> using slf4j then "force" a log implementation?
> >>
> >> Cheers
> >> --
> >> Massimo
> >> http://meridio.blogspot.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
