Spring framework dependency not deployed, must be satisfied by JBossESB (which is supposed to be optional)

Accroding to RiftSaw installation documentation (http://docs.jboss.org/riftsaw/releases/2.1.0.CR2/gettingstartedguide/html/installation.html#d0e53), deploying JbossESB is optional:

"2. Install JBossESB
This is only required if you want to run the ESB/BPEL examples."

However, when Riftsaw built from SVN trunk is deployed, the Spring dependency of some ODE artifacts (most notably riftsaw-bpel-store-2.2.0-SNAPSHOT.jar) isn't deployed anywhere in JBoss AS.

If JBossESB (which bundles Spring 2.5.6) is not deployed in the same JBoss AS installation, the ODE's dependency is not satisfied and attempts to deploy a BPEL process JAR result in a NoClassDefFoundError:

2010-07-09 15:26:14,416 INFO [org.apache.ode.store.ProcessStoreImpl] (Thread-21) Starting deployment of processes from directory "/opt/jboss-5.1.0.GA/server/ all/tmp/a2z168-4fefkl-gbf26vwg-1-gbf28dk5-ag/bpm-process-1.1.0.jar".
2010-07-09 15:26:14,477 ERROR [STDERR] (Thread-21) Exception in thread "Thread-21"
2010-07-09 15:26:14,478 ERROR [STDERR] (Thread-21) java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContext
2010-07-09 15:26:14,478 ERROR [STDERR] (Thread-21) at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:175)
2010-07-09 15:26:14,478 ERROR [STDERR] (Thread-21) at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.doDeploy(RiftSawProcessStore.java:176)
2010-07-09 15:26:14,479 ERROR [STDERR] (Thread-21) at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.run(RiftSawProcessStore.java:103)
2010-07-09 15:26:14,480 ERROR [STDERR] (Thread-21) Caused by: java.lang.ClassNotFoundException: org.springframework.context.ApplicationContext from BaseClassLoader@7a1116{VFSClassLoaderPolicy@1f7c6e1{name=vfsfile:/opt/jboss-5.1.0.GA/server/all/deploy/riftsaw.sar/ domain=ClassLoaderDomain@523df

{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.bootstrap.NoAnnotationURLClassLoader@1d05c81}

.........

I think that the RiftSaw deployment ant task should detect whether JBossESB is present in the target JBoss instance and if it isn't, deploy all dependencies that it would otherwise provide.