Yeah I noticed that when I checked the maven repo that it required
commons-collections, so I tried adding version 3.2.1. I ended up with the
following error:
java.lang.ClassCastException: wicket.extensions.Initializer cannot be cast
to org.apache.wicket.IInitializer
The maven repo stated that wicket-extensions required commons-collections
2.1, so I thought maybe it required an older version...same error. I went as
far as checking my local .m2 repo to make sure I didnt have a corrupted .jar
- which has happened to me before. The jar opens, able to see the
LRUmap.class file, so I am at a loss..
Is the dependency right? -->
<dependency>
<groupId>wicket</groupId>
<artifactId>wicket-extensions</artifactId>
<version>1.2.7</version>
</dependency>
I noticed that all the other wicket-related stuff is under groupId
org.apache.wicket. Googling around I found someone had this same error
awhile back using inconsistent versions of wicket and wicket-spring, but
that is definitely not the case here.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/wicket-extensions-alive-tp2324725p2324894.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
