On Thu, Apr 23, 2009 at 8:16 PM, Mike Edwards < [email protected]> wrote:
> ant elder wrote: > >> >> >> >> After some digging i've found the cause. I happen to have built the new >> implementation-spring* modules that are in the 2.x svn checkout but those >> modules are not yet in the main build as they're still being brought up in >> 2.x so most others and continuum wont have these built. With this change in >> r767428 the node launcher OSGi runtime finds and uses those tuscany-spring* >> jars because they're there in the modules/ directory hierarchy. Doing a "mvn >> clean" in the tuscany spring modules and the problem goes away and >> everything works fine. Is this the expected behaviour? >> >> ...ant >> >> Ant, > > Can you tell me more about the actual failure you're getting. > > I'm working on fixing the Spring modules, but it was not an expectation > that the new code in the Equinox launcher would have worked this way when > doing a build. > > > Yours, Mike. The actual error cause was: Caused by: java.lang.ClassNotFoundException: org.apache.tuscany.sca.assembly.builder.ComponentPreProcessor at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:481) but I guess thats just caused by the spring modules not being finished, I saw you committed some updates to the spring manifests last night so i've tried again now it it works ok fine today. What was unexpected (to me anyway at the time) was that the node-launcher-equinox tests were failing because it was discovering a module that i didn't even have included in the build just happened to be within the modules/ directory, so thats the bit i was asking if that was the expected behaviour. I'm not saying its a problem, now that i know this is whats going on i guess it wont be unexpected if it happens again. ...ant
