Scott,

Can you do a clean and then a build, and then attach the build output as a file?

Specifically, we're looking for lines like:

Copying 1 file to C:\labkey2.3\build\modules\experiment\pageflowTempDir

and

apt
Compiling 1 source file to C:\labkey2.3\build\modules\experiment\pageflowTempOutputDir

which indicate that the build process is successfully building the Beehive pageflows, which should result in XML files in directories like:

C:\labkey2.3\build\modules\experiment\pageflowTempOutputDir\_pageflow

Those should then be copied into a directory like:

C:\labkey2.3\build\modules\experiment\explodedMar\META-INF\_pageflow

which should then be rolled up into a file like:

C:\labkey2.3\build\labkeyWebapp\tempModules\experiment.module

which is actually a ZIP file. Inside, it should contain a META-INF/_pageflow directory. When the server starts up, it should copy the contents of that directory into your explodedWar/classes/_pageflow directory.

It's a somewhat complicated process, but it should give you a few other places to look to see where the chain might be broken. I can take a look at your build output and help diagnose as well.

Thanks,
Josh