Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 46 Next »

Check out how to integrate GPars into your projects.


Integration using Grape is very straightforward:


Grape config (optional)

GPars optionally relies on a couple of third-party libraries. Most of them reside in the central maven repository, however, since since the Netty lib resides in the jboss repository only, to leverage the (prototype) remoting capabilities, you either need to use the GrabResolver annotation (in Groovy 1.7):

or make sure your grapeConfig.xml file contains all the necessary maven repositories:


GPars is stored in the central maven repository at and also in the Codehaus maven repository at . To include GPars in your project add either of the following repositories and also the dependency into your project:



To include GPars in your project add the following (optional) repositories and dependencies into your project:

Sample maven-based Java API demo project

You may also like a stand-alone maven-based Java API sample project showing how to use GPars from Java and how to integrate GPars with Maven.

And the same sample project is available for the SNAPSHOT release.



GPars Grails plugin- grails install-plugin gpars

Grails since 1.2

Leveraging the build in dependency management you can instad installing the plugins update the BuildConfig.groovy file accordingly:


Using the Griffon built-in dependency management:

You may also consider using the plugins to enable GPars for older Griffon versions

GPars Griffon plugin - griffon install-plugin gpars


GPars itself depends on a couple of libraries from the maven central repository. Check out the GPars public pom:


Licensed under APL 2.0 - License

  • No labels