[WICKET-5028] Update Spring dependency because of classpath conflicts with cglib

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.5.0
• Fix Version/s: 7.0.0-M1
• Component/s: wicket-spring
• Environment: wicket-ioc
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Tom Götz
• Created: 06/Feb/13 15:14
• Updated: 28/Jun/13 10:14
• Resolved: 28/Jun/13 10:14

Description

Scenario:
I'm using Groovy (2.1.0) in my Wicket application which has a dependeny to asm 4.0. Wicket itself depends on cglib 2.2.2 which brings asm 3.3.1.

-> multiple versions of asm on the classpath -> not amused

So, I learned that Spring inlines cglib (3.0) and asm (4.0) since Spring 3.2. Would it be possible that Wicket - i.e. wicket-spring and/or wicket-ioc - depends on Spring 3.2.x, so that the dependeny to cglib can be dropped?

I'm attaching a patch to demonstrate what this could mean. Only drawback I discovered so far: wicket-ioc whould then depend on spring-core, currently there's no dependeny on Spring in wicket-ioc.

As an alternative we could also inline the required cglib/asm libs - as Spring also does - to avoid classpath conflicts with different version.