-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
multi module build problems #103
Comments
This is the expected behavior, and was required to address issue #99. Gradle has buildscript repositories, and project repositories. Before 3.3, Spotless loaded its formatters using the project repositories, but starting with 3.3 it uses the buildscript repositiories. This means you can use a private repository for your project dependencies, and keep it completely separate from the public gradle plugin repositories. When we made the change, we tried to make sure that there was a good clear error message, which should be right above where the stacktrace starts: Did you see this error message? spotless/plugin-gradle/src/main/java/com/diffplug/gradle/spotless/GradleProvisioner.java Line 41 in f8836ae
|
I understand. Thanks |
I'm actually surprised that a buildscript dependency on "https://plugins.gradle.org/m2/" (rather than By my understanding, Could someone explain to me where my understanding's gone wrong? |
plugins.gradle proxies to jcenter |
Okay, that makes sense to me now. Thanks for clearing up my misunderstanding @nedtwigg! |
In a multi module project, my root build.gradle file was simple, a buildscript declaration on top and the apply plugin in allprojects.
Upgrading from version 3.2.0 to 3.3.0 I must declare in allprojects the buildscript section to avoid build errors.
This is and example of my structure:
This is the error during build phase:
The text was updated successfully, but these errors were encountered: