-
Notifications
You must be signed in to change notification settings - Fork 565
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
Spotless apparently not configured properly #9117
Comments
@korthout could you have a look? Did we change anything recently? |
I just realized Nico is absent, probably for a while. As there's a workaround, I think we can wait until he's back, otherwise let me know and we can reassign. |
Considering this part:
This is something I had been running into when setting up spotless originally, and at the time I didn't understand why I just played around with it a bit, and it seems the problem is related to the maven reactor. Considering this part:
@pihme I'd be interested to see a situation where this diff occurs between running it locally and on CI. It's hard to say what's causing this without an example. Let me know if you encounter it again, or if you can point me to a CI run where this happened. We can also pair on this if you run into it again locally. |
9184: Support running `mvn spotless:apply` for convenience r=pihme a=korthout ## Description <!-- Please explain the changes you made here. --> When the spotless check fails, it recommends running `mvn spotless:apply` to automatically the formatting. However, if you try to run this locally you'll be greeted by the following message: > [ERROR] No plugin found for prefix 'spotless' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/Users/korthout/.m2/repository), central (https://repo.maven.apache.org/maven2)] -> [Help 1] The 'spotless' prefix is not available, because the first project that is run, is not the root-project but the zeebe-bom. And the zeebe-bom project does not have knowledge of the spotless plugin in its build plugins. This PR fixes this by adding the spotless plugin to the zeebe-bom's build plugins. Adding the plugin like this to the build doesn't do anything else except register the plugin for usage, because no executions are specified. The executions are still controlled by the profiles defined in the parent-pom. ## Related issues <!-- Which issues are closed by this PR or are related --> closes #9117 Co-authored-by: Nico Korthout <nico.korthout@camunda.com>
Description
Cannot really pinpoint the exact conditions, but lately I often have spotless errors in Jenkins.
mvn clean install -DskipTests -DskipChecks
does not change any filesmvn spotless:apply
results in this error: [ERROR] No plugin found for prefix 'spotless' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/peter/.m2/repository), central (https://repo.maven.apache.org/maven2)] -> [Help 1]Running
com.diffplug.spotless:spotless-maven-plugin:apply
does work. But it is a bit hard to rememberThe text was updated successfully, but these errors were encountered: