Migrate Nested Parent Maven Project to Gradle

Another note here about structure that might apply. The current structure for the source code is not aligned with what the end result structure looks like. Here is what the structure looks like:

• root
  • poms
    • sub-parent-1
      • pom.xml
    • sub-parent-2
      • pom.xml
    • sub-parent-3
      • pom.xml
    • sub-parent-4
      • pom.xml
  • services
    • service 1 (relies on parent 1)
    • service 2 (relies on parent 2)
    • … and so on.
  • libraries
    • library 1 (relies on parent 1)
    • library 2 (relies on parent 2)
    • … and so on.

Basically all of the children are logically organized by what they do, but within those they may have different parents, so the parent poms are organized in their own parent pom folders with no code to speak of behind them (just their configuration, plugins and dependencies).