You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9dfbab8
Browse filesBrowse the repository at this point in the historyBrowse files
Run the Spotless tests with the formatter inside the plugin
The Spotless tests declared the jars this build made in
palantirJavaFormat, which was the only way they could format: under
TestKit the default dependency had no version. They now run with
nothing declared, as a build that applies the plugin does, through the
jars the plugin carries.
BuildCacheTest keeps two tests of a declared formatter: declaring one
makes spotlessJava run again, and so does a change of the declared
jars. ConfigurationCacheTest keeps its test of the declared jars too,
and MultiProjectTest stays on a declared formatter, as resolving that
in the subprojects is what it tests.
With the step's formatter returning its input, every test that runs a
Spotless task still fails.
Copy file name to clipboardExpand all lines: gradle-open-java-format/src/test/java/com/palantir/javaformat/gradle/PalantirJavaFormatSpotlessPluginTest.java
+1-6Lines changed: 1 addition & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -32,11 +32,7 @@
32
32
@ValueSource(booleans = {true, false})
33
33
finalclassPalantirJavaFormatSpotlessPluginTest {
34
34
35
-
/** ./gradlew writeImplClasspath generates this file. */
36
35
// Forward slashes: the path goes into a Groovy string, where a Windows backslash would start an escape.
0 commit comments