Hi Josh,

My build process is just to zip up the module directory. Generally, during my development cycle I haven't even been doing that. I just edit the module directory in place and I manually tell tomcat to reload my labkey instance when needed. I have attached the module file.

will@lims:/usr/local/labkey-dev/externalModules/Fermentation$ zip -r ../Fermentation.module *
  adding: resources/ (stored 0%)
  adding: resources/config/ (stored 0%)
  adding: resources/config/module.xml (deflated 56%)
  adding: resources/schemas/ (stored 0%)
  adding: resources/schemas/dbscripts/ (stored 0%)
  adding: resources/schemas/dbscripts/postgresql/ (stored 0%)
  adding: resources/schemas/dbscripts/postgresql/fermentation-0.00-1.00.sql (deflated 18%)
  adding: resources/schemas/fermentation.xml (deflated 61%)
will@lims:/usr/local/labkey-dev/externalModules/Fermentation$ cd ..
will@lims:/usr/local/labkey-dev/externalModules$ jar tf Fermentation.module
resources/
resources/config/
resources/config/module.xml
resources/schemas/
resources/schemas/dbscripts/
resources/schemas/dbscripts/postgresql/
resources/schemas/dbscripts/postgresql/fermentation-0.00-1.00.sql
resources/schemas/fermentation.xml
will@lims:/usr/local/labkey-dev/externalModules$