The published POMs have broken project URLs as they refer to <url>https://github.com/diffplug/project</url> instead of <url>https://github.com/diffplug/spotless</url>, e.g. POM for Gradle plugin 5.10.1. This also applies for the SCM entry in each POM.
The problem arises because the rootProject name is deduced by the parent directory name and is then referenced from
|
url "https://github.com/${project.org}/${rootProject.name}" |
. Since CircleCI
by default checks out the repo in a directory called
project, Gradle picks that up as the default root project name. It's easily circumvented by setting the explicit root project name to
spotless in
settings.gradle. I've raised a related ticket
here on Gradle.
The published POMs have broken project URLs as they refer to
<url>https://github.com/diffplug/project</url>instead of<url>https://github.com/diffplug/spotless</url>, e.g. POM for Gradle plugin 5.10.1. This also applies for the SCM entry in each POM.The problem arises because the
rootProjectname is deduced by the parent directory name and is then referenced fromspotless/gradle/java-publish.gradle
Line 84 in e3a35d8
project, Gradle picks that up as the default root project name. It's easily circumvented by setting the explicit root project name tospotlessinsettings.gradle. I've raised a related ticket here on Gradle.