Stream: implementers
Topic: cyclic dependency
世界人 Sekaijin (Jan 29 2017 at 13:13):
Hi,
the hapi-fhir project content cyclic dependency.
the hapi-tinder-plugin depend on hapi-fhir-structures-dstu and hapi-fhir-structures-dstu2
and hapi-fhir-structures-dstu depend on hapi-tinder-plugin
and hapi-fhir-structures-dstu2 depend on hapi-tinder-plugin
I now correct the convergence problems of dependency and then I will try to find a solution
世界人 Sekaijin (Jan 29 2017 at 14:37):
It seems that they are unnecessary dependencies on tinder-plugin
世界人 Sekaijin (Jan 29 2017 at 16:17):
I found a solution
Dependencies are not required to hapi-tinder-plugin
They can be removed.
But the hapi-tinder-test project no longer compiles because the call to the hapi-tinder-plugin fails.
It lacks the dependencies to the execution.
Just add them and everything goes in order.
世界人 Sekaijin (Jan 29 2017 at 16:39):
Sorry
false joy. There are still difficulties
I continue
James Agnew (Jan 31 2017 at 03:03):
Hi Sekaijin,
The model dependencies in that plugin are for a previous version of the model, so it's technically not a cyclic dependency. They get fetched from Maven, as opposed to being built during the build cycle.
We use them basically to parse StructureDefinition, CodeSystem and ValueSet resources that are used as source for code generation.
James Agnew (Jan 31 2017 at 03:04):
And yeah, it's a bit messy.. but it works well, and this is only done at build-time for the library, there's no need to regular users to have to encounter this particular quirk.
Last updated: Apr 12 2022 at 19:14 UTC
