Hi,
Use 'mvn dependency:tree' to see which versions of wicket-core are in the
classpath.
Also check what is the content of target/theNameOfTheWar.war#WEB-INF/lib/
after 'mvn package'. There must be just one wicket-core.jar there
If this is OK then the problem is in Eclipse's configuration. You
I have gotten all the latest jars installed for the Wicket 6.15. I can verify
this in the Maven Dependencies directory.
For some reason, I feel it is still pointing to an older version of Wicket.
I am getting strange errors with the add method from the MarkupContainer.
Using the quick-start
