i have kind of a dumb question:
i recently posted a thread about merging a file-based module into the java based EHR module. in the java module, the view/query/reports folder get moved under the 'resources' folder. in a non-java module they are top-level.
in the past, i always pointed our server's externalModulesDir at a checked out version of the trunk's server/customModules/. this was quite convenient b/c I could just run a svn udpate and the server would get whatever changes i checked in. in practice pushing queries, views and other simpler things to the production server does not follow the labkey version cycle, and it probably wont any time soon.
yesterday on our staging server (running 10.2) i switched the externalModules folder to point to a copy of the trunk, with the newly merged EHR module. after restarting tomcat, none of the files located in /resources were showing up in labkey. in order for labkey to recognize the files located in /resources, do i need to copy a new ehr.module file onto the server? i presume this file would have the contents of /resources which get expanded into /labkeywebapp or something like that? or is this a 10.2/10.3 difference?
if that is the correct approach, will it be possible to continue updating the server by running 'svn update' i have historically been doing or will i constantly need to swap out the ehr.module file?
thanks in advance. |
| |
| jeckels responded: |
2010-09-17 09:58 |
Hi Ben,
We've removed almost all of the differences between Java and non-Java modules, but this is one of the last lingering issues.
Yes, in order to get the server to notice the files under the /resources directory you'll need to do a build and deploy ehr.module to your server. Doing "svn update" directly on the file system won't be sufficient.
Thanks,
Josh |
| |
| Ben Bimber responded: |
2010-09-17 10:16 |
ok. will this be a one time thing or do i need to push a new ehr.module each time i want to commit changes? |
| |
| jeckels responded: |
2010-09-17 10:18 |
Hi Ben,
You'll need to push a new ehr.module each time. The server should automatically detect the change, and as long as no Java code changed, deploy the new/updated file-based resources without needing to restart Tomcat.
Thanks,
Josh |
| |
| Ben Bimber responded: |
2010-09-17 13:58 |
ok. just to be sure i get it:
now that the ehr is a java module, there is no longer any reason to bother updating the code in the external modules folder (at least for this module), since the only way to update the file-based resources of a java module is to provide a new ehr.module file? is that correct? |
| |
| jeckels responded: |
2010-09-17 14:06 |
Hi Ben,
That's correct.
Thanks,
Josh |
| |
|
|