This looks like a dependency collision in Spring versions. We need to put a bug in JIRA[1] to go force the correct version of Spring-Data-Mongo.
https://rave.apache.org/issue-management.html On Mon, Jun 9, 2014 at 12:31 PM, Khazhismel Kumykov <[email protected]> wrote: > Heya, > > I'm trying to run Rave and Shindig using the mongodb support and am running > into an issue. > When shindig is starting up it runs into this error: > java.lang.NoClassDefFoundError: > org/springframework/core/DefaultParameterNameDiscoverer > at > > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.<init>(AbstractAutowireCapableBeanFactory.java:123) > Caused by: java.lang.ClassNotFoundException: > org.springframework.core.DefaultParameterNameDiscoverer > > I've tried this on latest master, tag 0.23 and tag 0.22, and ran into the > issue in all cases. > > I am building from source following using `mvn install -Pmongodb -Pdist` > and running the distribution archive to test. The rave portal does not > seem to run into this issue. > > I noticed in the shindig lib dir it has spring-beans-4.0.0.RC2 where as all > the other spring libs are 3.2.0.RELEASE. The portal war has > spring-beans-3.2.0.RELEASE. Swapping the incorrect 4.0.0.RC2 jar with the > 3.2.0.RELEASE jar fixes this issue. This isn't an ideal solution however. > > Running dependency:tree shows that somewhere along the line the incorrect > version is included due to a spring-data-mongodb dependency. > [INFO] +- > org.springframework.data:spring-data-mongodb:jar:1.0.3.RELEASE:compile > [INFO] | +- org.springframework:spring-tx:jar:3.2.0.RELEASE:compile > [INFO] | +- org.springframework:spring-beans:jar:4.0.0.RC2:compile > (version selected from constraint [3.0.7.RELEASE,4.0.0.RELEASE)) > > Not sure what the correct channel is for getting this issue resolved, any > help would be appreciated. > > Khazhy >
