This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop receiving this reminder on future updates to the PR.

I'll allow myself to merge this in without a review. I don't think anybody will object (but if anybody does, shout out).

Thank you @dweiss, I was just slow, was testing it out. I set the property locally, and added rule and test:

---
# yaml-language-server: $schema=https://raw.githubusercontent.com/ast-grep/ast-grep/refs/heads/main/schemas/rule.json
id: java-syntax
language: java
rule:
  kind: ERROR
message: Syntax Error
severity: error

---
# test the parser is working
id: java-syntax
valid:
  - x = 1;

I introduced bogus syntax to a file and the build then failed quickly on the problem (it is just an example and we probably should not do this):

> Task :testAstGrepRules
Running 1 tests

----------- Case Details -----------
PASS java-syntax  .

test result: ok. 1 passed; 0 failed;

> Task :applyAstGrepRules
error[java-syntax]: Syntax Error
    ┌─ lucene/core/src/java/org/apache/lucene/search/IndexSearcher.java:145:50
    │
145 │   public List<LeafReaderContext> getLeafContexts([) {
    │                                                  ^

Error: 1 error(s) found in code.
Help: Scan succeeded and found error level diagnostics in the codebase.


> Task :applyAstGrepRules FAILED

Sorry for not waiting, I wanted to proceed. Please open a new issue with those rules. This one looks very neat indeed - we can even force it to run prior to javac. It's a C based parser for java... remember jikes? :)