Skip to content

Conversation

@Pankraz76
Copy link
Contributor

@Pankraz76 Pankraz76 commented Feb 1, 2026

No description provided.

- name: assemble testClasses
run: ./gradlew assemble testClasses
- name: Spotbugs 🐞
run: ./gradlew spotbugsMain
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here seems to be no gate keeper, calling this goal:

- name: Error Prone 🚧️
run: ./gradlew assemble -DERROR_PRONE=true
- name: OpenRewrite ☑️ # 4m 55s
run: ./gradlew rewriteDryRun
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might extract this job to CRON job to make it optional as requested.

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionSha256Sum=0d585f69da091fc5b2beced877feab55a3064d43b8a1d46aeb07996b0915e0e0
distributionUrl=https\://services.gradle.org/distributions/gradle-9.3.0-bin.zip
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rewrite update.

return spotless.getRegisterDependenciesTask().getTaskService().get().provisionerFor(spotless);
}

protected final com.diffplug.spotless.extra.P2Provisioner p2Provisioner() {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

prone stuff but rewrite could cover this as well of course.


This makes it easier for the maintainers to quickly release your changes :)

## Check and format code
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems to be the critical point left behind last time. Communicating properly will help everybody to follow up as its done all over the other projects giving the convention and standard we also following.

This will make sure its better digested by the community.

@Pankraz76
Copy link
Contributor Author

prone example, should be simple to follow (c&p or allow patching later on) normally we have strong foundation no need to make invasive change.

* What went wrong:
Execution failed for task ':plugin-gradle:compileTestJava'.
> Compilation failed; see the compiler output below.
  /home/runner/work/spotless/spotless/plugin-gradle/src/test/java/com/diffplug/gradle/spotless/GradleIntegrationHarness.java:92: error: [UnnecessarilyFullyQualified] This fully qualified name is unambiguous to the compiler if imported.
40 actionable tasks: 7 executed, 33 up-to-date
  		return org.gradle.api.internal.provider.Providers.of(value);

  		                                       ^
      (see https://errorprone.info/bugpattern/UnnecessarilyFullyQualified)
    Did you mean 'return Providers.of(value);'?
  1 error

* Try:
> Check your code and dependencies to fix the compilation error(s)

@Pankraz76 Pankraz76 force-pushed the rewriteDryRun branch 2 times, most recently from 86f0156 to de1215b Compare February 1, 2026 12:10
* Spotless ✨
* `./gradlew spotlessApply`
* Spotbugs 🐞
* `./gradlew spotbugsMain`
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good UX - simple to interact (clickable)

Image

@Pankraz76 Pankraz76 force-pushed the rewriteDryRun branch 2 times, most recently from b9059ab to 3544119 Compare February 1, 2026 12:26
- name: Error Prone 🚧️
run: ./gradlew assemble -Derror-prone=true
- name: OpenRewrite ☑️ # 4m 55s
run: ./gradlew rewriteDryRun -DfailOnDryRunResults=false
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this will let corrupt code pass which is kind of the same having it optional, so its not applied at the end result. This makes it easy to activate once the community has adapted.

its just the same like spotless the the mechanism is nothing new at all. Let some time pass to see how its possible to integrate and then activate.

it takes some time yes 5 mins. the rewrite guys have 2 jobs because there war a hard 15 mins limit so in comparison it seems fast and acceptable.

whole build takes 8 mins with test so its in the range.

@Pankraz76
Copy link
Contributor Author

time is acceptable only double of the compile time:

image

@Pankraz76 Pankraz76 changed the title Pull #18820: Consolidate CI fix error-prone rewrite and spotbugs execution #2825 Pull #18820: Consolidate CI to fix error-prone rewrite and spotbugs execution #2825 Feb 1, 2026
}
// if there is \n on the end, remove it
if (!template.isEmpty() && ImportSorter.N.equals(template.get(template.size() - 1))) {
template.remove(template.size() - 1);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is clearly more complicated and therefore error-prone.

@Pankraz76 Pankraz76 force-pushed the rewriteDryRun branch 4 times, most recently from 4379ec6 to b973e5c Compare February 1, 2026 15:49
@Pankraz76
Copy link
Contributor Author

Pankraz76 commented Feb 1, 2026

kindly request your call on this, thanks.

@jbduncan @nedtwigg @Plunts

fyi @romani

@Pankraz76 Pankraz76 marked this pull request as ready for review February 1, 2026 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant