...
Index Viewer Additions (ex. ICD10CM) and Updates
Get index-viewer-data project from the repository from git.ihtsdotools.org via ssh.
Clone git project "https://git.ihtsdotools.org/ihtsdo/ihtsdo-mapping-tool-data.git" to local machine e.g. "C:\workspace-mapping-mars\ihtsdo-mapping-tool-data"
That that is a project with 2 sub-modules (empty, and icd10). Add a third, icd10cm
And lay it out like icd10 (e.g. just borrow everything you can).
1. All of the code to actually generate the files for the index viewer is in the mapping project itself. You’ll use that to generate the index files. (see above)
2. Put the index files into a project like the index-viewer-data project under icd10cm and version it appropriately
(e.g. give it a release version when you’re ready)
3. Build the project which will create a .zip file in the index-viewer-data/icd10cm/target directory. This can be done in eclipse or in cygwin from the index-viewer-data folder mvn clean build.
4. Log into nexus and add that .zip file as an artifact with the right groupId, artifactId, version
5. In the mapping project, make a mapping-config-prod-icd10cm config module
Look at how the “mapping-config-prod” works -> it has a dependency to the index veiwer data and imports it directly into there.
Thus, when the config project builds its zip file, it completely contains the index viewer data that is needed for that deployment. Then when that gets unpacked into the .war file, the index data is all in the right place in the deployed war package.
...