-
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
Add groovy formatter to maven #697
Conversation
f91067e
to
1976908
Compare
ee30c0e
to
d070f14
Compare
Thanks for a great PR, looks good. The way that the README works is not intuitive, you edited the top part correctly, but you needed to run In the Gradle plugin, we call this step greclipse. I think it's confusing to have two steps with the same name (two different |
d671249
to
2631076
Compare
@nedtwigg |
Nope, it shouldn't. CircleCI is having issues :(
I'm gonna let this rest for 24 hours in case other maintainers have comments. Once that 24 hrs has passed and our CI providers comes back online, we'll merge and release. |
@nedtwigg |
Yes, CircleCI is just down today is all. Bummer that it fails danger, rather than safe. I'll figure out CI tonight, I don't wanna spend time on it while it's still flaky. |
CI is fixed now. I'll merge and release tomorrow, barring any objections. |
Released in |
After creating the PR, please add a commit that adds a bullet-point under the
-SNAPSHOT
section of CHANGES.md, plugin-gradle/CHANGES.md, and plugin-maven/CHANGES.md which includes:If your change only affects a build plugin, and not the lib, then you only need to update the
CHANGES.md
for that plugin.If your change affects lib in an end-user-visible way (fixing a bug, updating a version) then you need to update
CHANGES.md
for both the lib and the build plugins. Users of a build plugin shouldn't have to refer to lib to see changes that affect them.This makes it easier for the maintainers to quickly release your changes :)