Korbinian, No. You add a different jar depending on which logging system you use. The base slf4j jar is already in the pom. But the "plugin" jar which interfaces with your chosen logging system must be added by yourself.
Take a look at slf4j when you get a chance. It's a very nice logging system. This style of using a different jar for whatever logging system helps get away from some hacks that commons-logging had to work with. Thanks, On Fri, 2006-12-29 at 09:14 -0600, Ryan Sonnek wrote: > can't this be added to the wicket POM so that all wicket 2.0 projects > automatically pick it up? > > On 12/29/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote: > > > > I added it to the Wicket 2.0 Migration Page on the Wiki, hope this is ok. > > > > Regards > > > > > -----Ursprüngliche Nachricht----- > > > Von: Igor Vaynberg [mailto:[EMAIL PROTECTED] > > > Gesendet: Freitag, 29. Dezember 2006 08:56 > > > An: [email protected]; [email protected] > > > Betreff: wicket 2.0 migrated to slf4j > > > > > > i have just migrated wicket 2.0 from commons-logging to slf4j > > > as was previously discussed and agreed upon. > > > > > > people using 2.0 need to add the following to their project's pom or > > > equivalent: > > > > > > if you are using commons-logging: > > > > > > <dependency> > > > <groupId>org.slf4j</groupId> > > > <artifactId>slf4j-jcl</artifactId> > > > <version>1.1.0</version> > > > </dependency> > > > > > > > > > if you are using log4j > > > > > > <dependency> > > > <groupId>org.slf4j</groupId> > > > <artifactId>slf4j-log4j12</artifactId> > > > <version>1.1.0</version> > > > </dependency> > > > > > > these jars will bind slf4j to the proper logging library > > > > > > if you are using another logging impl like jdk see slf4j > > > website for the appropriate binding jar > > > > > > -igor > > > > > > > -- Philip A. Chapman Desktop and Web Application Development: Java, .NET, PostgreSQL, MySQL, MSSQL Linux, Windows 2000, Windows XP
signature.asc
Description: This is a digitally signed message part
