This was introduced by f7543b2, which only updated the logic for for JDK 17+.

Fixes #1127

PiperOrigin-RevId: 659616575

This CL also implements some minimal formatting behavior _around_ `{@snippet ...}` (namely, a blank line before and after). It does not make any effort to change formatting _inside_ `{@snippet ...}`, only to stop reflowing it blindly.

PiperOrigin-RevId: 665555661

Fixes the error on startup by loading the service when needed and not when the class is initializing.  IntelliJ docs on this, https://plugins.jetbrains.com/docs/intellij/plugin-services.html#retrieving-a-service.

Tested locally with IntelliJ versions 2021.3 and 2024.2.

#1134 has bug #1132 tagged, but I don't think it does anything to resolve the issue in it's current state. (I do agree that getting on the newer IntelliJ tooling is beneficial though, it offers inspections that catches issues like this.)

Fixes #1132.

Fixes #1138

COPYBARA_INTEGRATE_REVIEW=#1138 from nrayburn-tech:fix/1132 5866980
PiperOrigin-RevId: 665876052

Hello,

I have no experience in IntelliJ plugin development, but maybe I can support you that the required invest in time isn't that high. As far as I can tell the `gradle build` works.

Due to the changes of the IntelliJ gradle plugin I was urged to raise the java compatibility to 17 as well as the supported IntelliJ version to at least 2022.3 (see [requirements](https://plugins.jetbrains.com/docs/intellij/tools-intellij-platform-gradle-plugin.html#requirements))

#1132

Fixes #1134

COPYBARA_INTEGRATE_REVIEW=#1134 from mmaeller:gh-1132 abed210
PiperOrigin-RevId: 665880070

PiperOrigin-RevId: 665921070

Setting it to "" creates a broken plugin, but omitting it sets it to the same as
since-build. So apparently you have to do this.

PiperOrigin-RevId: 665927556

Fixes #1136

PiperOrigin-RevId: 666125973

* ebnf-mode: Last change 13 years ago with open PR from phst from 2019.  For the sake of the current package version metadata work, just slap in a pkg.el file for now.
* llm-goose: Missing header.
* gyp: Missing header.
* lv: Include pkg.el added earlier.

PiperOrigin-RevId: 667696660

#1153

PiperOrigin-RevId: 673574143

Fixes #1153.

Fixes #1161

COPYBARA_INTEGRATE_REVIEW=#1161 from dweiss:1153-block-line-comments-in-java23 e3ed83c
PiperOrigin-RevId: 674304999

The intent was to only run the test on JDK 23+ and to disable it until the linked issue was fixed, but it actually resulted in the test being discovered and run on all JDK versions.

That's fine, because the test is backwards compatible (`///` comments are valid in all versions, they just aren't markdown comments until 23).

The test is being fixed in #1161

PiperOrigin-RevId: 674352956

PiperOrigin-RevId: 675207795

Despite documentation to the contrary, the column numbers are already 1-indexed. The comment was added in unknown commit when g-j-f was still implemented using ecj instead of javac, so maybe it was true then?

PiperOrigin-RevId: 681451766