Migrate Nested Parent Maven Project to Gradle

Help/Discuss
1

Hello everyone! I am not certain if this has been posted before but I wasn’t able to find it, so my apologies if it has been answered (and please point me to the answer if so!).
I am trying to migrate a Maven project to gradle using the latest (version 6.6) gradle release.
gradle init succeeds without issue, however I notice that a number of my shared dependencies are not making it over. After a little digging, it looks like what is happening is that the init is not migrating our “middle tier” parents over as well. This is where I am stuck, since I think this should be possible (maybe?). Here is what the build structure looks like:

  • Project Root Pom
    • Sub Parent Pom 1
      • Project 1
      • …
      • Project N
    • Sub Parent Pom 2
      • Project 1
      • …
      • Project N
    • Sub Parent Pom 3
      • Project 1
      • …
      • Project N
    • Sub Parent Pom 4
      • Project 1
      • …
      • Project N

Where every actual project has a “middle” parent and that middle parent is a child of the root. this enables managing of shared dependencies for all of the projects organized under a specific parent.
My question is: is there a way to use gradle init to capture this type of multi-inheritance model automatically or do I need to go in manually and recreate this (or the equivalent in gradle)?

Thank you so much in advance for your help!
Ben

2

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).