This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
Anyway, is there more to that stack trace. It looks like you didn't paste the entire stack trace. Look at the very bottom of your stack trace to find the root cause exception and post that please.
Frank VanOor wrote:Hi Joachim , thanks for suggestion.
I removed spring-tomcat-weaver , it compiled fine but still have the same exception.
I didn't find version 2.3.0 of spring-webflow. The version I found is 1.0.6. I added this version, but still same exception.
When you build, in your target directory, what are the third party jars that get packaged with your application. Look at them and tell us if you see any duplicates with different version numbers.
Have you considered that the groupId changed for the new SpringWebFlow versions?
But as Mark mentioned: it would be best to have a look in your target directory for duplicates.
Frank VanOor
Ranch Hand
Joined: Jun 18, 2004
Posts: 41
posted
0
H Mark,
You were right !!! I looked into the Target directory and indeed, lots of Spring 2.5.6 jars were still sitting there. I did a maven clean which removes the content of Target, made a new build, deploy and the Exception isn't happening anymore.
You were right !!! I looked into the Target directory and indeed, lots of Spring 2.5.6 jars were still sitting there. I did a maven clean which removes the content of Target, made a new build, deploy and the Exception isn't happening anymore.