...

Administering plugins

...

Creating a plugin

• You can create a plugin as part of a maven build using the car-maven-plugin.
• You can create a plugin "virtually" by installing a deployed application from a running Geronimo server acting as a plugin repository.
• You can create a plugin using the Geronimo administration console to create or edit the plugin metadata.

...

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.

...

1. If the server is running, stop the server.
2. Copy the new jar into the appropriate directory in your geronimo server's repository. For instance: Code Block mkdir -p repository/org/foo/myjar/1.1/ cp ~/newFooJar/myjar-1.1.jar repository/org/foo/myjar/1.1/ Alternatively, the administration 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.

...

...