THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Starting with Geronimo 2.1 the servers are assembled entirely out of plugins.
...
This document is organized in the following sections:
...
Plugin basics
A Geronimo plugin is a jar-structured file that contains a META-INF/geronimo-plugin.xml descriptor following this schema:
...
...
Most plugins are Geronimo modules which means they include a classloader description, service configurations ("gbeans"), and possibly classes and resources. For instance, if you deploy a javaee application on geronimo, it turns into a geronimo module containing the description of the app's classloader, gbean configurations for the javaee components (web apps, ejbs, etc), and the classes and resources from your application. The additional information in the Geronimo plugin descriptor includes:
...
Here's an example of a car-maven-plugin configuration using maven dependencies and configuring most of the additional information possible:
...
...
As you use maven to build plugins, a geronimo-plugins.xml plugin catalog is automatically maintained in your local maven repository. You can force this to be rebuilt by running
...
...
This might be necessary if you prune your maven repository and remove plugins listed in the catalog.
...
Similarly you can use the gshell deploy/assemble-server command specifying the same information on the command line or interactively.
...
...
In order to get a working server you must include the geronimo-boilerplate-minimal plugin which includes several files used to start the server
...
TODO: The groupId is not currently used but the intention is to copy the assembled server into an appropriate maven repository.
...
TODO: get gshell to accept line continuations as in the following (these DO NOT WORK IN REAL LIFE):
...
...
Assembling a server using maven.
The easiest way to assemble a server is to use maven and the car-maven-plugin. The dependencies from your pom will be installed in your server, and if they are plugins they will be installed as modules with all dependencies and stuff unpacked and metadata installed into the correct files. Here's a simple example assembling a server that supports Roller and includes the basic admin console.
...
...
Upgrading jars and plugins to a new version
...
If the jar is to be installed as part of a plugin installation, see the section below. Otherwise, follow these steps. First, if the server is running, stop the server. Second, copy the new jar into the appropriate directory in your geronimo server's repository. For instance:
...
...
Alternatively, the admin console portlet Services->Repository can be used to add artifacts to the server's repository.
Finally, after the new jar is installed in the server's repository, add a line to var/config/artifact_aliases.properties (or the equivalent file, if the server is using a non-standard alias file). For instance, to replace myjar-1.0.jar with myjar-1.1.jar:
...
...
With this configuration, the server will substitute myjar-1.1.jar for any myjar-1.0.jar dependency.
...
If the jar is installed as part of a plugin installation, you can include configuration upgrade information in the geronimo-plugin.xml. During plugin installation, the upgraded jar will be automatically installed. This is easiest to specify in the car-maven-config configuration in the pom.xml, prior to building the plugin.
...
...