hmmm...
seems that the 2.0 reference came from wicket 1.3 beta 2 pom file...
however excluding it and adding the correct version(2.0.6?) as suggested
in the link to nabble does not work either...
cwilkes wrote:
Also I would look in the server's common/lib and other directories. And do a
"mvn clean" to clean out any old jars that might be in the local target/
directory.
Looking that maven's logs there a "org.springframework:spring:jar:2.0" in
there. I'm not sure when the createConcurrentMapIfPossible method was
introduced, maybe it was later in the 2.0.x series. See
http://www.nabble.com/Can-wicket-spring-just-depend-on-spring-context-and-spring-web--tf4125986.html#a11733423
on how to write the exclusion part in your pom.xml to get rid of the
"spring.jar" dependency.
Luke Taylor wrote:
It looks like a maven dependency issue.
Check the WEB-INF/lib directory of your expanded webapp and look for
multiple spring version jars in there. Then fix your maven build file to
exclude the inconsistent ones.
Nino Saturnino Martinez Vazquez Wael wrote:
Hi We keep getting this error from some of the spring stuff:
java.lang.NoSuchMethodError:
org.springframework.core.CollectionFactory.createConcurrentMapIfPossible(I)Ljava/util/Map;
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.<init>(DefaultSingletonBeanRegistry.java:82)
--
Luke Taylor. Monkey Machine Ltd.
PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
