openjdk/jdk@a917fb3

Fixes: #898
PiperOrigin-RevId: 512759236

I'm going to add tests next, but with this weird file structure I've been using, there's no good place to put them.

The only content changes here are in build.gradle.

PiperOrigin-RevId: 512914783

Also support optimizing imports, using the ImportOptimizer API.

PiperOrigin-RevId: 513562756

PiperOrigin-RevId: 513589436

…Activity.

PiperOrigin-RevId: 513811140

Pop up this warning once per-project per-launch, only when the Formatter is enabled (or at startup if the formatter is already enabled in the project).

PiperOrigin-RevId: 513822794

I moved the description out of the Gradle config and into the XML. (It was just in the gradle so we could add the gjf version number, but that seems unnecessary since I changed the versioning so that the plugin version matches the gjf version.)

I also updated the IntelliJ Gradle plugin to 1.13.1 because plugin publishing is broken in 1.13.0.

PiperOrigin-RevId: 513888985

I don't really understand _why_ this works. I'm able to (easily) reproduce the
problem by not including the `=` in my `idea64.options` file. But then if I
copy/paste the command line out of `ps`, it works fine.

And since it's easy enough to change this, I'm inclined to just do that?

Fixes #908.

PiperOrigin-RevId: 514440074

Previously, blank lines could only be emitted before comments if they were there in the input. This was irrespective of BlankLineWanted.YES hints in the OpBuilder.

These hints are already being set by some paths in GJF, so now that they're respected, blank lines will be added to some existing files.

Eval in unknown commit

PiperOrigin-RevId: 514817708

PiperOrigin-RevId: 515682100

… use gjf.

Right now if your IDE isn't set up properly and you have gjf enabled in a
project, you get a single warning. Any uses of the code formatter after that
will instead use the built-in formatter.

This is confusing to people who don't notice the notification. They think gjf
is formatting their code strangely. Instead, let's warn on every single
invocation of the formatter until they either fix the configuration issue or
disable gjf in the project.

Fixes #914 #919.

PiperOrigin-RevId: 515722447

I have a feeling this is causing a lot of the issues people are seeing where
it's constantly trying to reformat and failing because of syntax errors.
Hopefully this will make it only try to reformat when a user specifically
requests it.

PiperOrigin-RevId: 521657519

javac no longer accepts these, see https://bugs.openjdk.org/browse/JDK-8027682

PiperOrigin-RevId: 525775880