GMaven is dead...should Spock be used with Groovy Eclipse Compiler for Maven?

[Nick Vaidyanathan]

These docs suggest not to use GMaven for compilation:
http://groovy.github.io/gmaven/

Instead favoring this compiler:
http://docs.codehaus.org/display/GROOVY/Groovy-Eclipse+compiler+plugin+for+Maven

The Spock Maven setups I've been following (from the framework docs on integration with Maven) use GMaven. Does anyone have a pithy example on using the new compiler?

...though I guess this could be a good push to learn/use Gradle. Do most Spock users use Gradle as their build system?

[Marcin Zajączkowski]

On 2014-03-15 10:17, Nick Vaidyanathan wrote:
> These docs suggest not to use GMaven for compilation:
> http://groovy.github.io/gmaven/
>
> Instead favoring this compiler:
> http://docs.codehaus.org/display/GROOVY/Groovy-Eclipse+compiler+plugin+for+Maven

There is also https://github.com/groovy/GMavenPlus which seems to
actively developed (Disclaimer: I use Gradle to build Groovy code and
have no experience with GMavenPlus).

> The Spock Maven setups I've been following (from the framework docs on
> integration with Maven) use GMaven. Does anyone have a pithy example on
> using the new compiler?
>
> ...though I guess this could be a good push to learn/use Gradle. Do most
> Spock users use Gradle as their build system?

Groovy code compilation (also mixed with Java code) works out of the box
in Gradle and there is also no problems with Spock.

Marcin

--
http://blog.solidsoft.info/ - Working code is not enough

[renu chudamani]

Have you attempted to use the groovy eclipse compiler? I have all our projects configured with the following in our pom - and it works successfully:

<plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.1</version>
                <configuration>
                    <compilerId>groovy-eclipse-compiler</compilerId>
                    <verbose>true</verbose>
                    <includes>
                        <include>*Spec.*</include>
                    </includes>
                </configuration>
                <dependencies>
                    <dependency>
                        <groupId>org.codehaus.groovy</groupId>
                        <artifactId>groovy-eclipse-compiler</artifactId>
                        <version>2.8.0-01</version>
                    </dependency>
                    <dependency>
                        <groupId>org.codehaus.groovy</groupId>
                        <artifactId>groovy-eclipse-batch</artifactId>
                        <version>2.1.8-01</version>
                    </dependency>
                </dependencies>
            </plugin>
            <plugin>
                <groupId>org.codehaus.groovy</groupId>
                <artifactId>groovy-eclipse-compiler</artifactId>
                <version>2.8.0-01</version>
                <extensions>true</extensions>
            </plugin>
        </plugins>

[Jan Bols]

You might also use GMavenPlus. See http://docs.codehaus.org/plugins/servlet/mobile#content/view/238354461 for an overview of the different maven build options available. 

Personally, i use the groovy eclipse plugin, but I wish they 'd have less open bugs.

Greetings

Jan

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spockframewor...@googlegroups.com.
To post to this group, send email to spockfr...@googlegroups.com.
Visit this group at http://groups.google.com/group/spockframework.
For more options, visit https://groups.google.com/d/optout.

[James Cook]

Is that last plugin (org.codehaus.groovy:groovy-eclipse-compiler) necessary? I ask because I do not have it in my build. What does it do?

-- jim