gradle-consistent-versions adds optional dependency on root project to Maven POM

[hugoo10]

Hello, I just switched from square/javapoet and I noticed a weird dependency in the pom:

https://repo1.maven.org/maven2/com/palantir/javapoet/javapoet/0.6.0/javapoet-0.6.0.pom

<dependency>
  <groupId>com.palantir.javapoet</groupId>
  <artifactId>javapoet-root</artifactId>
  <version>0.6.0</version>
  <scope>runtime</scope>
  <optional>true</optional>
</dependency>

my issue is that this artifact doesn't exist and when i'm doing mvn dependency:go-offline it tries to download this dependency and falls into error.
Can you fix that?

[adamretter]

This is still a problem with in JavaPoet 0.7.0 and can be seen here - https://repo1.maven.org/maven2/com/palantir/javapoet/javapoet/0.7.0/javapoet-0.7.0.pom#L29

The issue seems to come from - https://github.com/palantir/javapoet/blob/0.7.0/settings.gradle#L11

The problem is that there is no javapoet-root published to Maven Central.

For us, this means that JavaPoet cannot be used in projects that need CI. Could perhaps @pkoenig10 @cushon @carterkozak take a look at this issue please?

[pkoenig10]

This is a result of using gradle-consistent-versions. I'm going to transfer this issue.