Okay, I'm checking out a new version, compile it (./build.sh) and then call ./build.sh functionaltests. A lot of tests fail because that class I mentioned previously is not found.

Also, why am I compiling the AOP examples if all I want to do is to run the functional tests ? There is an error message related to AOP too (see below). Also, why do we have the aopc compiler spit out messages at the (so it seems) TRACE level ? Can we make this less verbose ? Is JBossCache CVS head currently broken ? Otherwise I would expect that the sequence CVS checkout, compile, run testsuite always works !

bela@dell /cygdrive/c/JBossCache $ ./build.sh functionaltests Buildfile: build.xml compile-classes14: [javac] Compiling 1 source file to C:\JBossCache\output\test- classes [copy] Copying 38 files to C:\JBossCache\output\etc [copy] Copying 1 file to C:\JBossCache\output\resources compile-classes50-1: aopc-pojocache: [aopc] [info] Total length of filenames to be compiled is greater than 1000, listing files in --SOURCEPATH: c:\DOCUME~1 \BELA~1.DEL\LOCALS~1\Temp\src49385.tmp [aopc] [debug] Passed in instrumentor: null [aopc] [debug] Defaulting instrumentor to: org.jboss.aop.instrument.ClassicInstrumentor [aopc] [debug] Passed in advisor: null [aopc] [debug] Defaulting advisor to: org.jboss.aop.ClassAdvisor [aopc] [debug] jboss.aop.class.path is NULL [aopc] [debug] jboss.aop.search.classpath: 'null' true [aopc] [debug] jboss.aop.path: C:\JBossCache\output\resources \jboss-aop.xml -- Bela Ban Lead JGroups / Manager JBoss Clustering Group JBoss - a division of Red Hat