Now that we have the real need to release the parent POMs, I figured out that there's something I did not think through: circular dependencies.
Even if we use Maven version ranges (e.g., <version>[1.0, 2.0)</version>) for snapshot versions, we would have to specify a proper fixed version when we release the code.
Each of the life.qbic dependencies found in <dependencyManagement> uses the parent POM. Updating a version on one of the dependencies means that we have to update the version of the parent POM, which in turn means that we have to update POM files deriving from the parent POM. That's where we have a "chicken and egg" problem.
The easiest solution is to remove all the life.qbic dependencies from the parent POM.
Now that we have the real need to release the parent POMs, I figured out that there's something I did not think through: circular dependencies.
Even if we use Maven version ranges (e.g.,
<version>[1.0, 2.0)</version>
) for snapshot versions, we would have to specify a proper fixed version when we release the code.Each of the
life.qbic
dependencies found in<dependencyManagement>
uses the parent POM. Updating a version on one of the dependencies means that we have to update the version of the parent POM, which in turn means that we have to update POM files deriving from the parent POM. That's where we have a "chicken and egg" problem.The easiest solution is to remove all the
life.qbic
dependencies from the parent POM.