Sorry I'm a bit late with this thread, but just weighing in here... Upgrading SLF4j can cause breakages, because people will go and depend on slf4j-log4j or whatever for their project, and they'll need to go and update that dependency to keep things in sync. This causes unexpected breakage. It's not worth the pain caused by this sort of thing, unless we need to update to pull in a bug fix, as Martijn says.
Regards, Al On Tue, Mar 25, 2008 at 10:22 PM, Martijn Dashorst < [EMAIL PROTECTED]> wrote: > wicket itself doesn't, but something *cough*spring*cough* does, and it > gets included in our examples project. > > Martijn > > On 3/25/08, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > > commons-logging? Seriously?? *shudders* > > > > Why does wicket depend on commons-logging when slfj is used? > > > > > > On Tue, Mar 25, 2008 at 3:54 PM, Timo Rantalaiho <[EMAIL PROTECTED]> > wrote: > > > On Tue, 25 Mar 2008, Martijn Dashorst wrote: > > > > -1 > > > > > > > > Upgrading these kind of things in a stable release is not > preferred. > > > > Like Gerolf says: it is unclear which dependencies these projects > > > > have, whether they have Java 5 deps etc. > > > > > > > > Upgrading to maintenance versions should be ok but frowned upon, > minor > > > > or major version upgrades should not be done at all in a > maintenance > > > > release. The only caveat is when a bug in a dependency has a > direct > > > > impact on wicket code, and the bug is only solved in a minor or > major > > > > version update. > > > > > > OK, maybe it's better to be conservative here. ...Though > > > getting old versions as transitive dependencies is frowned > > > upon ;) > > > > > > > > > > > > Best wishes, > > > Timo > > > > > > -- > > > Timo Rantalaiho > > > Reaktor Innovations Oy <URL: http://www.ri.fi/ > > > > > > > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.2 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2 >
