On 18.06.2016 13:40, Mr Andersson wrote: [...]
I've tried:<dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy</artifactId> <version>2.4.7</version> </dependency> as well as <plugin> <inherited>true</inherited> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.5.1</version> <configuration> <source>${java.version}</source> <target>${java.version}</target> <!--!!!!!!!!!!!!!!!! ALSO TRIED WITHOUT THESE TWO LINES !!!!!!!!!!!!!!!! --> <compilerId>groovy-eclipse-compiler</compilerId> <verbose>true</verbose> <!-- See: http://stackoverflow.com/questions/17944108/maven-compiler-plugin-always-detecting-a-set-of-sources-as-stale --> <useIncrementalCompilation>false</useIncrementalCompilation> </configuration> <dependencies> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-eclipse-compiler</artifactId> <version>2.9.2-01</version> </dependency> </dependencies>
according to https://github.com/groovy/groovy-eclipse/wiki/Groovy-Eclipse-Maven-plugin you need to define a dependency for groovy-eclipse-batch as well
</plugin> but this results in an error when a Java class is referencing a Groovy class in the project.
where did you store your java and groovy source files?
I am not using eclipse. What are the neccesary steps to get Groovy to work *seamlessly in a Groovy project in 2016* ? What are the limitations? Thanks!
you can always try the gmavenplus plugin... or migrate to gradle, it works much better there for me ;)
bye blackdrag
