This message was deleted.

Do you mean you have dependencies declared in the parent pom that are missing now? Gradle does not follow that concept of parent/child POMs and does not really support it. And while you could manipulate the POM to have the parent set, you shouldn't, especially as for example a Gradle consumer would use the improved Gradle Module Metadata instead of the POM and then also miss those dependencies. So you would also need to disable the Gradle Module Metadata, ...