Grape lets you quickly add maven repository dependencies to your classpath. Here are the most common solutions:
Yes, you can annotate an import in Groovy. You can also search for dependencies on mvnrepository.com and it will provide you the @Grab annotation form of the pom.xml entry.
Not all dependencies are in maven central. You can add new ones like this:
Some maven dependencies need classifiers in order to be able to resolve. You can fix that like this:
Sometimes you will want to exclude transitive dependencies as you might be already using a slightly different but compatible version of some artifact. You can do this as follows:
Because of the way JDBC drivers are loaded, you'll need to configure Grape to attach JDBC driver dependencies to the system class loader. I.e:
From groovysh use the method call variant:
If you are behind a firewall and/or need to use Groovy/Grape through a proxy server, you can specify those settings on the command like via the http.proxyHost and http.proxyPort system properties:
Or you can make this system wide by adding these properties to your JAVA_OPTS environment variable:
If you want to see what Grape is doing set the system property "groovy.grape.report.downloads" to "true" (e.g. add "-Dgroovy.grape.report.downloads=true" to JAVA_OPTS) and Grape will print the following infos to System.error:
Grape (The Groovy Adaptable Packaging Engine or Groovy Advanced Packaging Engine) is the infrastructure enabling the grab() calls in Groovy, a set of classes leveraging Ivy to allow for a repository driven module system for Groovy. This allows a developer to write a script with an essentially arbitrary library requirement, and ship just the script. Grape will, at runtime, download as needed and link the named libraries and all dependencies forming a transitive closure when the script is run from existing repositories such as Ibiblio, Codehaus, and java.net.
Grape follows the Ivy conventions for module version identification, with naming change.
group- Which module group the module comes from. Translates directly to a Maven groupId or an Ivy Organization. Any group matching
/groovy[x][\..*]^/is reserved and may have special meaning to the groovy endorsed modules.
module- The name of the module to load. Translated directly to a Maven artifactId or an Ivy artifact.
version- The version of the module to use. Either a literal version '1.1-RC3' or an Ivy Range '[2.2.1,)' meaning 2.2.1 or any greater version).
The downloaded modules will be stored according to Ivy's standard mechanism with a cache root of
One or more groovy.lang.Grab annotations can be added at any place that annotations are accepted to tell the compiler that this code relies on the specific library. This will have the effect of adding the library to the classloader of the groovy compiler. This annotation is detected and evaluated before any other resolution of classes in the script, so imported classes can be properly resolved by a @Grab annotation.
grab(...) call will be added to the static initializer of the class of the containing class (or script class in the case of an annotated script element).
In order to use a Grape annotation multiple times you must use the Grapes annotation, e.g.:
Otherwise you'll encounter the following error:
Typically a call to grab will occur early in the script or in class initialization. This is to insure that the libraries are made available to the ClassLoader before the groovy code relies on the code. A couple of typical calls may appear as follows:
* Multiple calls to grab in the same context with the same parameters should be idempotent. However, if the same code is called with a different ClassLoader context then resolution may be re-run.
grabis disabled by default. Starting calling
Grape.initGrape()will enable grab. Any calls to grab before
initGrape()is called will be ignored. Hence Grape managed classloading is opt in only. Multiple calls ti
Grape.initGrape()after the first successful call are ignored.
argsmap passed into the
grabcall has an attribute
noExceptionsthat evaluates true no exceptions will be thrown.
grabrequires that a RootLoader or GroovyClassLoader be specified or be in the ClassLoader chain of the calling class. By default failure to have such a ClassLoader available will result in module resolution and an exception being thrown
initGrape()has been called).
classLoader:argument and it's parent classloaders.
referenceObject:argument, and it's parent classloaders.
group:- <String> - Which module group the module comes from. Translates directly to a Maven groupId. Any group matching
)/is reserved and may have special meaning to the groovy endorsed modules.
module:- <String> - The name of the module to load. Translated directly to a Maven artifactId.
version:- <String> and possibly <Range> - The version of the module to use. Either a literal version '1.1-RC3' or an Ivy Range '[2.2.1,)' meaning 2.2.1 or any greater version).
classifier:- <String> - The Maven classifier to resolve by.
conf:- <String>, default 'default' - The configuration or scope of the module to download. The default conf is
default:which maps to the maven
force:- <boolean>, defaults true - Used to indicate that this revision must be used in case of conflicts, independently of
changing:- <boolean>, default false - Whether the artifact can change without it's version designation changing.
transitive:- <boolean>, default true - Whether to resolve other dependencies this module has or not.
There are two principal variants of
grab, one with a single Map and one with an arguments Map and multiple dependencies map. A call to the single map grab is the same as calling grab with the same map passed in twice, so grab arguments and dependencies can be mixed in the same map, and grab can be called as a single method with named parameters.
There are synonyms for these parameters. Submitting more than one is a runtime exception.
classLoader:- <GroovyClassLaoder> or <RootClassLoader> - The ClassLoader to add resolved Jars to
refObject:- <Object> - The closest parent ClassLoader for the object's class will be treated as though it were passed in as
validate:- <boolean>, default false - Should poms or ivy files be validated (true), or should we trust the cache (false).
noExceptions:- <boolean>, default false - If ClassLoader resolution or repository querying fails, should we throw an exception (false) or fail silently (true).
Grape added a command line executable 'grape' that allows for the inspection and management of the local grape cache.
This installs the specified groovy module or maven artifact. If a version is specified that specific version will be installed, otherwise the most recent version will be used (as if '*' we passed in).
Lists locally installed modules (with their full maven name in the case of groovy modules) and versions.
This returns the file locations of the jars representing the artifcats for the specified module(s) and the respective transitive dependencies. You may optionally pass in -ant, -dos, or -shell to get the dependencies expressed in a format applicable for an ant script, windows batch file, or unix shell script respectively. -ivy may be passed to see the dependencies expressed in an ivy like format.
If you need to change the directory grape uses for downloading libraries you can specify the grape.root system property to change the default (which is ~/.groovy/grape)
//TODO expand on discussion of grapeConfig.xml
You can customize the ivy settings that Grape uses by creating a ~/.groovy/grapeConfig.xml file. If no such file exists, here are the default settings used by Grape:
For more information on how to customize these settings, please refer to the Ivy documentation.
If you find yourself wanting to reuse artifacts that you already have locally in your Maven2 repository, then you can add this line to your ~/.groovy/grapeConfig.xml:
And further customize your Grape configuration:
Using Apache Commons Collections:
Using Google Collections:
Launching a Jetty server to serve Groovy templates:
Grape will download Jetty and its dependencies on first launch of this script, and cache them. We're creating a new Jetty Server on port 8080, then expose Groovy's TemplateServlet at the root of the context — Groovy comes with its own powerful template engine mechanism. We start the server and let it run for a certain duration. Each time someone will hit http://localhost:8080/somepage.gsp, it will display the somepage.gsp template to the user — those template pages should be situated in the same directory as this server script.