Groovy-Eclipse provides a compiler plugin for Maven. Using the compiler plugin, it is possible to compile your maven projects using the Groovy-Eclipse compiler.
|
The most recent version of the Groovy-Eclipse-Compiler plugin for maven is
2.6.0-01.
If necessary, 2.6.1-01-SNAPSHOT versions will be available from *http://nexus.codehaus.org/snapshots/*.
|
How to use the compiler plugin---Setting up the POM
In your plugin section, you must change the compiler used by the
maven-compiler-plugin. Like the
javac ant task, the maven-compiler-plugin does not actually compile, but rather delegates the compilation to a different artifact (in our case, the
groovy-eclipse-batch
artifact):
t;build>
...
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<compilerId>groovy-eclipse-compiler</compilerId>
<verbose>true</verbose>
</configuration>
<dependencies>
<dependency>
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-eclipse-compiler</artifactId>
<version>2.6.0-01</version>
</dependency>
</dependencies>
</plugin>
...
</plugins>
</build>
By default, this will use Groovy 1.8.4 to compile your code. If you would prefer to use 1.7.10, then add another dependency to the maven-compiler-plugin:
t;dependency>
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-eclipse-batch</artifactId>
<version>1.7.10-06</version>
</dependency>
This will allow Groovy files to be compiled. The groovy-eclipse-compiler recognizes all settings supported by the
maven-compiler-plugin.
Note that the groovy-eclipse-compiler and groovy-eclipse-batch artifacts are available in Maven-central, so there is no need to explicitly declare any extra repositories.
Setting up the source folders
There are several ways to set up your maven project to recognize Groovy source files
Do nothing
The simplest way to set up your source folders is to do nothing at all: add all of your Groovy files to
src/main/java
and src/test/java
. This requires absolutely no extra configuration and is easy to implement. However, this is not a standard maven approach to setting up your project. If you require a more standard maven approach, then
it is possible to put your Groovy files in src/main/groovy
and
src/test/groovy
and you Java files in src/main/java
and
src/test/java
. There are several ways of doing this.
Do almost nothing
If there is at least one file (Java or not) in src/main/java
, then all files in
src/main/groovy
will be found. If, however, src/main/java
is empty, then
src/main/groovy
will be ignored. You can get around this by placing an empty file in
src/main/java
just so that src/main/groovy
will be recognized. The same is true for
src/test/java
and src/test/groovy
. This is actually a workaround for
GRECLIPSE-1221.
Use the groovy-eclipse-compiler
mojo for configuring source folders
(You only need this approach if your project has an empty src/main/java
or
src/test/java
.)
If your project has no Java files and you don't want to add an empty file in
src/main/java
, then you can configure source files by referencing the groovy-eclipse-compiler mojo. Just add this to the
plugins
section of your pom:
t;build>
...
<plugin>
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-eclipse-compiler</artifactId>
<version>2.6.0-01-SNAPSHOT</version>
<extensions>true</extensions>
</plugin>
...
</build>
The <extensions>true</extensions>
section is important because this redefines the default lifecycle of your project so that an extra phase is added. This phase has an extra goal attached to it that adds the two Groovy source folders.
Use the
build-helper-maven-plugin
(You only need this approach if your project has an empty src/main/java
or
src/test/java
.)
The build-helper-maven-plugin
allows you to do things like adding extra source folders to your project without needing to redefine the default lifecycle. You need to add this configuration to your build plugin section:
t;build>
...
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.5</version>
<executions>
<execution>
<id>add-source</id>
<phase>generate-sources</phase>
<goals>
<goal>add-source</goal>
</goals>
<configuration>
<sources>
<source>src/main/groovy</source>
</sources>
</configuration>
</execution>
<execution>
<id>add-test-source</id>
<phase>generate-test-sources</phase>
<goals>
<goal>add-test-source</goal>
</goals>
<configuration>
<sources>
<source>src/test/groovy</source>
</sources>
</configuration>
</execution>
</executions>
</plugin>
...
</build>
The benefit of using this approach is that you do not need to make any changes to the default lifecycle. The downside is, of course, that you need 31 lines of configuration to do this!
Sample project and source code
There is an archetype available for this project. You can use it through a command like this:
n archetype:generate \
-DarchetypeGroupId=org.codehaus.groovy \
-DarchetypeArtifactId=groovy-eclipse-quickstart \
-DarchetypeVersion=2.5.2-01 \
-DgroupId=foo \
-DartifactId=bar \
-Dversion=1 \
-DinteractiveMode=false \
-DarchetypeRepository=https:
A
sample project using the compiler plugin as well as the source code for the plugin itself are available from the Codehaus.org subversion repository:
|
The SVN repository URL is:
https://svn.codehaus.org/groovy/eclipse/trunk/extras
There are several projects in the repository:
-
groovy-eclipse-compiler : the compiler plugin itself (an m2eclipse project).
-
groovy-eclipse-batch-builder : a set of ant scripts and configuration files used to build the
groovy-eclipse-batch artifact. This artifact is an amalgamation of all jars required for compiling Groovy and Java code in Eclipse, including ecj (the Eclipse compiler for Java), the non-UI components of Groovy-Eclipse, the Groovy jars, and various
required Eclipse bundles.
-
groovy-eclipse-maven-tests : a sample project that uses the compiler plugin (an m2eclipse project).
-
org.codehaus.groovy.m2eclipse : an Eclipse plugin that provides integration between Groovy-Eclipse and m2eclipse (the Maven tooling for Eclipse).
-
Feature org.codehaus.groovy.m2eclipse : an Eclipse feature that is required for building and releasing the
org.codehaus.groovy.m2eclipse plugin.
|
The sample project and archetype is not maintained as well as we would like. Some community help with this would be greatly appreciated. Please see
GRECLIPSE-1285.
Why another Groovy compiler for Maven? What about GMaven?
There are several benefits that the compiler plugin provides over GMaven, but at the same time it has a few limitations. First, the benefits:
- The compiler plugin does not require the creation of Java stubs so that your Groovy files can compile against Java files. This will prevent some arcane compile errors from appearing.
- The Groovy-Eclipse compiler is the same inside Eclipse and inside Maven, and so configuration across the two platforms can be simplified.
- The compiler plugin is a
standard compiler plugin for Maven. It therefore follows all allows all the same standard configuration that the Javac compiler plugin uses. This makes it simpler to introduce Groovy into an existing Maven project. All you need to do is change the compiler
plugin that the pom references.
There are some limitations:
- GroovyDoc tool is not supported because the compiler plugin does not produce stubs.
- Groovy Mojos are not supported.
- Groovy scripts cannot be executed in your poms.
- Groovy compiler options are not passed through to the compiler.
- The
defaultScriptExtension
compiler option is not supported.
Whether or not the Groovy-Eclipse compiler plugin for Maven is appropriate for your project will depend on your requirements.
Project Lombok
Project Lombok is compatible with the groovy-eclipse-compiler. There is some extra configuration that you need to do. The lombok jar needs to be added to
both the build and compile dependencies sections:
t;dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>0.10.4</version>
</dependency>
Also, the following configuration needs to be added to the maven-compiler-plugin configuration:
t;configuration>
<compilerId>groovy-eclipse-compiler</compilerId>
<verbose>true</verbose>
<compilerArguments>
<javaAgentClass>lombok.core.Agent</javaAgentClass>
</compilerArguments>
<fork>true</fork>
</configuration>
分享到:
相关推荐
适用于eclipse3.5的groovy-eclipse插件
groovy-2.0.8-with-eclipse-plugin-2.7.2.part3
groovy-2.0.8-with-eclipse-plugin-2.7.2.part1
groovy-2.0.8-with-eclipse-plugin-2.7.2.part2
Eclipse Groovy插件 Eclipse Groovy插件 Eclipse Groovy插件 Eclipse Groovy插件
jenkins集成sonarqube的groovy插件sonar-groovy-plugin-1.5.jar
赠送Maven依赖信息文件:groovy-3.0.9.pom; 包含翻译后的API文档:groovy-3.0.9-javadoc-API文档-中文(简体)版.zip; Maven坐标:org.codehaus.groovy:groovy:3.0.9; 标签:groovy、codehaus、jar包、java、中文...
赠送Maven依赖信息文件:groovy-all-2.4.13.pom; 包含翻译后的API文档:groovy-all-2.4.13-javadoc-API文档-中文(简体)版.zip; Maven坐标:org.codehaus.groovy:groovy-all:2.4.13; 标签:all、groovy、codehaus...
赠送Maven依赖信息文件:groovy-all-2.4.5.pom; 包含翻译后的API文档:groovy-all-2.4.5-javadoc-API文档-中文(简体)版.zip; Maven坐标:org.codehaus.groovy:groovy-all:2.4.5; 标签:codehaus、groovy、all、...
Groovy-Plugin-eclipse 4.7版本-在线下载的插件-附说明,想在网上下载别人下载好的,又怕别人动过手脚,死磕在线下载,好几次才成功,放心使用!
赠送Maven依赖信息文件:groovy-3.0.9.pom; 包含翻译后的API文档:groovy-3.0.9-javadoc-API文档-中文(简体)-英语-对照版.zip; Maven坐标:org.codehaus.groovy:groovy:3.0.9; 标签:groovy、codehaus、jar包、...
groovy-eclipse插件features和plugins完整版,自己在线安装生成的,直接放到eclipse相关目录就可以使用。
赠送Maven依赖信息文件:groovy-2.5.1.pom; 包含翻译后的API文档:groovy-2.5.1-javadoc-API文档-中文(简体)-英语-对照版.zip; Maven坐标:org.codehaus.groovy:groovy:2.5.1; 标签:codehaus、groovy、中英对照...
apache-groovy-3.0.8.zip apache官网的groovy3.0.8版本,希望大家多多下载,apache-groovy-3.0.8.zip apache官网的groovy3.0.8版本,希望大家多多下载,apache-groovy-3.0.8.zip apache官网的groovy3.0.8版本,希望...
最近的groovy-all-2.4.12.jar包供使用,解决as编译时报错问题
org.gradle.api.resources.ResourceException: Could not get resource '...下载groovy-all-2.4.15.jar后,放入对应的 android-studio/gradle/gradle-5.*/lib/目录。 重启 Android Studio 及可使用。
apache-groovy-sdk-4.0.1下载
groovy-all-2.4.15.jar文件,MAC使用时需存放在/Users/用户名/.gradle/caches/jars-3/某一缓存目录下,找不到就都看一下,我遇到的问题是缓存目录中下载的是2.4.17版本,应该跟gradle版本升级有关
groovy-all-2.4.8.jar
groovy-2.3.6-installer windows安装版本