Add ability to use the generated parser instead of the source grammar

README.md

@@ -64,6 +64,12 @@ because the interpreter is language agnostic.
 For the same reasons, if your parser and/or lexer classes extend a custom implementation of the 
 base parser/lexer classes, your custom code will *not* be run during live preview. 
 
+As of 1.17, this limitation is partially not true. The configuration window of a grammar has a new option
+that allows using the generated parser code in the preview. In this case, the grammar must be compiled into
+a Java class (just to be on Project's target classpath). Any changes made to such grammar are not immediately
+reflected in the preview and the project must be recompiled instead. It is also possible to specify the name of the
+compiler parser/lexer class. By default the name of the grammar is used (parser and lexer grammar).
+
 ## History
 
 See [Releases](https://github.com/antlr/intellij-plugin-v4/releases)

build.gradle

@@ -20,8 +20,8 @@ apply plugin: 'org.jetbrains.intellij'
 apply plugin: 'antlr'
 
 compileJava {
-    sourceCompatibility = '1.8'
-    targetCompatibility = '1.8'
+    sourceCompatibility = '11'
+    targetCompatibility = '11'
 }
 
 intellij {

gradle.properties

@@ -1,4 +1,4 @@
-pluginVersion=1.19.2
+pluginVersion=1.19.2-akovari
 
 # e.g. IC-2016.3.3, IU-2018.2.5 etc
 # For a list of possible values, refer to the section 'com.jetbrains.intellij.idea' at
@@ -16,7 +16,7 @@ pluginVersion=1.19.2
 
 #ideaVersion=IC-2021.2
 
-ideaVersion=IC-2021.3.3
+ideaVersion=IC-2022.2
 
 # The version of ANTLR v4 that will be used to generate the parser
 antlr4Version=4.10.1

historical-contributors-agreement.txt

@@ -64,4 +64,4 @@ YYYY/MM/DD, github id, Full name, email
 2019/11/24, nopeslide, Uffke Drechsler, [email protected]
 2020/12/05, roggenbrot, Sascha Dais, [email protected]
 2021/11/04, OleksiiKovalov, Oleksii Kovalov, [email protected]
-
+2021/06/04, akovari, Adam Kovari, [email protected]