Issues with POMs in the repo (Circular dependency from Core to Test-Core and POM dependencies are structured differently than other services)

The POMs in this service are structured differently than other services. In other services, the parent pom contains almost no dependencies and allows the Core & Test-Core POMs to specify dependencies individually.

In addition, the Test project is tightly coupled to the build of the Core creating a circular dependency.

In the root POM, the following is observed:

  <modules>
    <module>workflow-core</module>
    <module>provider/workflow-azure</module>
    <module>provider/workflow-gcp</module>
<!--    <module>provider/workflow-ibm</module> Fix: Missing classes-->
    <module>provider/workflow-gcp-datastore</module>
    <module>testing/workflow-test-core</module>
  </modules>

Note that the module testing/workflow-test-core is referenced in the modules list. The test modules should know about the core modules, but not the other way around.

If the test module is removed from the build list, the project fails to compile successfully.