Not true. People need to add a <dependencyManagement> section where they specify the version of the SLF4J api. This overrules any version set in our POM.
If this were true, *all* our dependencies need to become provided, which is rubbish, since it negates the whole purpose of transitive dependencies. Unless someone comes with a convincing argument, I'm inclined to revert this one (at least for the slf4j-api jar, the slf4j-log4j12 and log4j jars are optional imo). Martijn On Mon, Jan 26, 2009 at 8:31 PM, <[email protected]> wrote: > Author: ivaynberg > Date: Mon Jan 26 19:31:06 2009 > New Revision: 737795 > > URL: http://svn.apache.org/viewvc?rev=737795&view=rev > Log: > making slf4j deps provided otherwise everyone downstream has to add > exclusions if using a different ver > > Modified: > wicket/trunk/pom.xml > > Modified: wicket/trunk/pom.xml > URL: > http://svn.apache.org/viewvc/wicket/trunk/pom.xml?rev=737795&r1=737794&r2=737795&view=diff > ============================================================================== > --- wicket/trunk/pom.xml (original) > +++ wicket/trunk/pom.xml Mon Jan 26 19:31:06 2009 > @@ -318,17 +318,20 @@ > <groupId>org.slf4j</groupId> > <artifactId>slf4j-api</artifactId> > <version>1.4.2</version> > + <scope>provided</scope> > </dependency> > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-log4j12</artifactId> > <version>1.4.2</version> > + <scope>provided</scope> > </dependency> > <dependency> > <groupId>log4j</groupId> > <artifactId>log4j</artifactId> > <version>1.2.13</version> > <optional>true</optional> > + <scope>provided</scope> > </dependency> > <dependency> > <groupId>org.springframework</groupId> > > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
