OHDSI Component Dependencies

[anthonysena]

The current pom.xml is still lagging behind in terms of the other OHDSI dependencies. As of the moment, here is the current configuration and the proposed updates:

dependency	owner	pom reference	target version	changes	actions
SqlRender	@schuemie, @chrisknoll	1.6.4-SNAPSHOT	1.6.8	OHDSI/SqlRender@v1.6.4...v1.6.8	none
FeatureExtraction	@schuemie, @anthonysena	2.2.4	3.1.0	OHDSI/FeatureExtraction@v2.2.4...v3.1.0	none
Hydra	@schuemie	0.0.11	0.1.1	OHDSI/Hydra@v0.0.11...v0.1.1	released
circe-be	@chrisknoll	1.9.0-SNAPSHOT	1.9.0	OHDSI/circe-be@v1.8.6...master	release to nexus
standardized-analysis-specs & standardized-analysis-utils	@anton-abushkevich	1.2.1-SNAPSHOT	1.3.0	OHDSI/StandardizedAnalysisAPI@v1.1.0...master	version update & nexus release
SkeletonCohortCharacterization	@anton-abushkevich	1.2.0-SNAPSHOT	1.2.0	OHDSI/SkeletonCohortCharacterization@v1.1.0...master	version update & nexus release

In the table above, I've noted the dependencies with each component's owner. Additionally the actions column notes what action(s) are required for each component. Those labeled as 'none' represent those Java components that are released to the OHDSI nexus repo and can be referenced in the pom.xml. Those labeled 'release to nexus' will require a release when we're done testing. For the others labeled 'version update & nexus release', we'll need to: increment the version to the target version with the -SNAPSHOT suffix, update the pom.xml in WebAPI's master branch to reference it and then run through testing. Assuming those work, we'll then release to the nexus repo and then ensure that the pom.xml is using the fixed, released versions.

I'll make some updates to the pom.xml for those that are finalized. @schuemie only tagging you here for awareness - no actions required on your part.