-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. Martijn On 3/25/08, Timo Rantalaiho <[EMAIL PROTECTED]> wrote: > On Tue, 25 Mar 2008, Gerolf Seitz wrote: > > i just went through our dependency list in wicket-parent/pom.xml to > > check for new releases for the dependencies. > > maybe we want to upgrade some of them: (current version in our pom in > > parentheses) > > > > slf4j-api-1.5 (1.4.2) > > slf4j-log4j12-1.5 (1.4.2) > > log4j-1.2.15 (1.2.13) > > mx4j-3.0.2 (3.0.1) > > commons-lang-2.4 (2.1) > > commons-logging-1.1.1 (1.1) > > joda-time-1.5.2 (1.4) > > commons-httpclient-3.1 (3.0.1) > > portals-bridges-common-1.0.4 (1.0.3) > > > It would be a good idea to update these already in 1.3.3 to > get early feedback on how they work, and fix the versions in > 1.3.x / 1.4.x as needed. > > As a rule of thumb one should always depend on the latest > stable versions of things, and if these fail there is always > the easy workaround of excluding the transitive dependency > provided by wicket and including whatever version you want. > > WDYT? > > 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
