How to set up GMavenPlus in my Maven project?

Add the plugin configuration to your pom.xml file, specifying the Groovy version and source directories. Refer to the wiki for detailed examples, as the README only provides high-level guidance.

GMavenPlus vs Gradle for Groovy projects

GMavenPlus is best for existing Maven projects needing Groovy integration, while Gradle offers native Groovy support with simpler DSL-based builds. Choose based on your build tool preference and project constraints.

Does GMavenPlus work with the latest Groovy version?

Yes, it generally supports recent Groovy releases, but you must specify the Groovy version in the plugin configuration. Check the Maven site or wiki for compatibility details, as updates might lag behind Groovy releases.

How to migrate from the old GMaven plugin to GMavenPlus?

Replace the GMaven plugin dependency in pom.xml with GMavenPlus and update configuration elements. The wiki likely has migration guides, but be prepared for potential breaking changes in plugin parameters.

Can I use GMavenPlus for Spock testing in Maven?

Yes, GMavenPlus compiles Groovy test sources, making it suitable for Spock tests. Ensure Spock dependencies are included, and configure the plugin to handle test compilation phases appropriately.

What are common compilation errors with GMavenPlus?

Errors often arise from misconfigured source directories, incompatible Groovy versions, or missing dependencies. Review the plugin logs and consult the wiki for troubleshooting steps, as documentation is not self-contained.

Open-Awesome

GMavenPlus

NOASSERTIONJava5.1.0

A Maven plugin for integrating Groovy into Maven projects, enabling mixed Java/Groovy builds.

GitHub

306 stars43 forks0 contributors

What is GMavenPlus?

GMavenPlus is a Maven plugin that enables the integration of Groovy programming language into Maven-based projects. It allows developers to compile Groovy source files, manage dependencies, and build mixed Java/Groovy applications seamlessly within the Maven build lifecycle. The plugin solves the problem of incorporating Groovy's dynamic features into standardized Maven workflows without requiring complex custom build configurations.

Target Audience

Java and Groovy developers working in Maven-based projects who need to incorporate Groovy code for scripting, testing, or application logic. It is particularly useful for teams maintaining legacy GMaven projects or building new applications with mixed-language architectures.

Value Proposition

Developers choose GMavenPlus because it is a maintained, reliable rewrite of the original GMaven plugin, offering better compatibility with modern Maven versions and Groovy releases. Its straightforward integration reduces build configuration complexity compared to manual Groovy setup or alternative build tools.

Overview

A rewrite of GMaven, a Maven plugin for Groovy

Use Cases

Best For

Adding Groovy scripts to existing Maven-based Java projects
Writing Spock tests in Maven projects for behavior-driven development
Building applications that mix Java and Groovy source files
Migrating from the legacy GMaven plugin to a supported alternative
Leveraging Groovy's metaprogramming features in enterprise Maven builds
Simplifying build configurations for Groovy-based libraries or tools

Not Ideal For

Projects using Gradle or other build tools with native Groovy support
Teams building lightweight applications where Maven's overhead is unnecessary
Developers needing real-time Groovy script execution without compilation
Environments prioritizing pure Java without dynamic language dependencies

Pros & Cons

Pros

Modern Rewrite

As a rewrite of the original GMaven plugin, it provides improved reliability and maintainability, addressing issues in legacy setups.

Seamless Maven Integration

Integrates directly into Maven's lifecycle phases like compile and test, allowing Groovy code to be processed alongside Java without external tools.

Mixed Source Support

Handles projects with both Java and Groovy source files, managing cross-language dependencies automatically during the build.

Dependency Management

Automatically manages Groovy runtime dependencies, ensuring compatibility with project libraries and reducing configuration errors.

Cons

Documentation Fragmentation

The README primarily points to external wiki and Maven site for usage details, which can hinder quick setup and troubleshooting.

Maven Lock-in

Requires projects to use Maven, making it irrelevant for teams preferring Gradle, Ant, or other build systems with built-in Groovy support.

Configuration Complexity

For developers new to Maven plugins, setting up GMavenPlus involves XML configuration in pom.xml, which can be more verbose than alternatives like Gradle scripts.

Frequently Asked Questions

Related Projects

Jenkins job-dsl-plugin

A Groovy DSL for Jenkins Jobs

Stars1,924

Forks819

Last commit12 days ago

Lazybones

A simple project creation tool that uses packaged project templates.

Stars617

Forks101

Last commit5 years ago

skeletal

A simple project creation tool that uses packaged templates

Stars21

Forks4

Last commit7 months ago

travis-groovy

execute groovy scripts on travis-ci

Stars3

Forks0

Last commit8 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub