-
Notifications
You must be signed in to change notification settings - Fork 459
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
Fix conflicts between Spotless and Android re: clean
task
#1014
Conversation
Wow, I've just been down the rabbit hole that is issue #429! To summarise, it looks like our ktlint test was flaking for a long time because it was using JCenter to download ktlint, and switching to Maven Central on I also understand that this flakiness was aggravated at one point by our use of detached configurations in So I suppose my only query is: will the If so, then I have no other concerns. The rest of this PR LGTM! 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the @Disabled
annotation in the ktlint test file, this PR looks good to me.
No. We are using the gradle retry plugin so that flaky dependency resolutions get a chance to retry. But even with that, we still got a failure, but only on shyiko The shyiko stuff is quite old, ktlint has lived at |
Ah okay, I understand. This seems acceptable to me, then. LGTM. :) |
Shipped in |
Spotless eagerly applies
BasePlugin
for the purpose of creating theclean
task. This causes a problem for users who define their ownclean
task, which the Android template recommends.Now we don't have to anymore, because we find it lazily (and without triggering configuration) like so:
spotless/plugin-gradle/src/main/java/com/diffplug/gradle/spotless/SpotlessPlugin.java
Lines 56 to 62 in 581215b