cwilkes wrote:
Currently the 1.3.0-beta2 version of wicket-parent and wicket-spring depend on the large single "spring" jar. Can this be changed to just depend on the org.springframework artifacts spring-context and spring-web?
This is one of those things that seems like a good idea until you realise that for it to work properly, you need to update all the POMs in the maven 2 repository at the same time. ;-)
If something else depends on the full Spring (e.g. Hibernate) then that gets brought in too. You can therefore end up with nasty version conflicts which are dependent on the order your Spring JARs happen to be defined on the classpath.
Additionally, the individual Spring modules don't have the source published on the Maven 2 repo, which is a pain.
So no, I don't think we should change this. Sorry. ;-) Regards, Al -- Alastair Maw Wicket-biased blog at http://herebebeasties.com
