If script is part of project's classpath (in source folder and does not match a script filter), config script is applied.Two paths exist when running a Groovy Script from a project that supplies a compiler configuration script: Run As > Groovy Script - config script handling Modulepath entries are not yet supported for Groovy sources classpath entries work as expected. It can be combined with any supported version of Groovy. GROOVY-9153: PR #947 - merged for 2.5.8, 3.0b2Īs of Eclipse 4.12, Java 12 is fully supported within the IDE.Please note that parser recovery is not implemented for the Parrot Parser, so your editing experience may be sub-par in this mode. To enable it, add -Dgroovy.antlr4=true to your eclipse.ini file after the -vmargs line or add a compiler config script to your project with uginFactory = .ParserPluginFactory.antlr4(configuration).

The new Parrot Parser is disabled by default in Groovy 3. New and Noteworthy Support for new versions of Groovy Only plugin version 0.12.1 solves the just re ran my tests with all versions starting from 0.12.1 and I must have made a mistake before because now the results show that the problem only starts with version 0.13.1, in the versions before that (0.12.1-0.13.0) the folder does get added to the build path.Greclipse 3.4.0 was released on June 29th 2019. With any other version, like 0.13.0 or 0.14.0 the sources do get generated as I can see them under target, but they don't get added to the build path.Ĭhanging java executable to the one from JDK also does not help (and I don't quite understand how that should help anyways). After I change the plugin version, i just hit ALT+F5 for 'Maven Update Project' and the generated sources folder gets added to the eclipse build bath. So what works for me is using plugin version 0.12.1. In fact, when I run mvn clean install (from the eclipse run menu) I don't get the folder added to build path even when using the only working plugin version, which is 0.12.1.

This should all happen when I change pom.xml and hit Update Project (ALT+F5). I have the same my understanding, I don't need to run a maven build (mvn clean install) to get the code generated & added to build path. I got an error on the in the pom.xml : Execution default of goal 2:maven-jaxb2-plugin:0.13.1:generate failed: A required class was missing while executing 2:maven-jaxb2-plugin:0.13.1:generate: com/sun/xml/bind/api/ErrorListenerĪnd the genared-sources folder is not added to the build path :

The genared-sources folder is added to the build path : $/generated-sources/jaxbĪfter a mvn clean install with 0.12.1, no problem.

Eclipse neon.2 no menu bar