Your module won't automatically get built by the Ant script, even if it's in the standard module directory.

To get your module added to the server's list, you'll need to either add it to the core system build (in <LABKEY_ROOT>/server/build.xml, add it to the lists in the "build_classes_parallel" and "build_classes_sequential" targets), or directly invoke the build.xml that was included as part of your module. Either way, you should end up with a helloworld.module in <LABKEY_ROOT>/build/deploy/modules, which will make the server notice it at startup time.

Thanks, Josh

Not really sure what you mean to do when invoking the build.xml directly? Tried right clicking and selecting Make Module 'helloworld' but I don't think that's what you mean. Or is it just one of the ant targets you can use to invoke it?

In any case, I added a new target to the main build.xml file:

<target name="helloworld">
       <antcall target="sub_build_module">
           <param name="moduleName" value="helloworld" />        </antcall>
   </target>

(Possibly this is what you meant above? Have this target and then running that target from the list of ant scripts)

And, then did you what you mentioned above. Adding the antcall to both build_classes_parallel and build_classes_sequential

<antcall target="helloworld" />

its now appearing in the list of modules.

...Now to figure out how these work :)

Yes, that's what I meant, though I forgot to mention that you'd need to introduce the new target for helloworld as well.

You could potentially use the build.xml that's inside of your module's directory (and either run it from the command line or add it to the list of build.xml files that IntelliJ looks at), but it's probably easiest to take the approach that you did with adding a new target.

Thanks, Josh

i.e. the demo module creates a demo schema, but this is not accessible through schema browser.

For security reasons, we don't automatically expose all of the schemas and tables in the underlying database. In many cases, for example, the schema won't include a container column and you don't want a user who has access to any folder on the server to be able to access it.

If you have Java code, you can choose how to expose your tables. The simplest example is in org.labkey.api.module.SimpleModule - check out the startupAfterSpringConfig() method. It exposes all of the underlying database schemas that the module declares.

Thanks, Josh

For a file based module, the above method won't work. You instead need to just copy the directory to the module directory. So the target name would instead be:

<target name="helloworld" >
       <copy todir="${deploy.modules.dir}/helloworld">
           <fileset dir="${basedir}/customModules/helloworld">
           </fileset>
       </copy>
   </target>

With potential include or exclude elements inside the fileset node, to filter out particular files.