Skip to content
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

Merged
merged 5 commits into from
Sep 17, 2020
Merged

Conversation

bitwiseman
Copy link
Contributor

@bitwiseman bitwiseman commented Sep 15, 2020

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:

  • a summary of the change
  • either
    • a link to the issue you are resolving (for small changes)
    • a link to the PR you just created (for big changes likely to have discussion)

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 :)

@nedtwigg
Copy link
Member

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 spotlessApply so that it would render into the actual markdown. I also added docs by copying the equivalent docs from gradle.

In the Gradle plugin, we call this step greclipse. I think it's confusing to have two steps with the same name (two different Eclipse classes in the maven plugin). We should either rename it to Greclipse or GroovyEclipse, no preference from me.

@bitwiseman
Copy link
Contributor Author

@nedtwigg
Thanks! I updated it to greclipse.

@bitwiseman
Copy link
Contributor Author

It looks like your checks are not behaving well. Should this say "All checks have passed" when only one check has run?

Screen Shot 2020-09-16 at 9 33 01 AM

@nedtwigg
Copy link
Member

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.

@bitwiseman
Copy link
Contributor Author

@nedtwigg
Do have you added all the checks to the required checks list for the main branch? (Just to make sure no one accidentally merges when not all checks have run.)

@nedtwigg
Copy link
Member

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.

@nedtwigg
Copy link
Member

CI is fixed now. I'll merge and release tomorrow, barring any objections.

@nedtwigg nedtwigg merged commit 6a1f09d into diffplug:main Sep 17, 2020
@nedtwigg
Copy link
Member

Released in plugin-maven 2.4.0.

@bitwiseman bitwiseman deleted the maven-groovy branch September 22, 2020 16:01
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.

2 participants