Aliasing jars and modules

You may want to change the version of jars or plugins from those used when you geronimo server was assembled, or completely replace one with another. This can be done for any artifact in the geronimo repository, but not for jars in the lib directory. We hope to move almost all the jars out of lib shortly, but this is not yet possible.

Recall that the geronimo repository, like a maven 2 repository, is structured like

for an artifact

To install a new version of an artifact you typically need to create a new directory corresponding to the version, then copy the artifact into that directory. There is an admin console page that helps with this.

Dependencies in geronimo plugins can be specified with or without a fixed version. If all the dependencies on the artifact you are replacing are specified without a fixed version, you can simply add your new artifact to the appropriate place in the geronimo repository and, if the version is newer than the old artifact, it will be used by geronimo the next time the plugins that use it are started. If your artifact has a lower version than what it is replacing, you need to remove the old artifact.

If at least one dependency is specified with a fixed version or you are using a different artifact, you need to specify the replacement more explicitly. For the main geronimo server this would be in the var/config/artifact_aliases.properties file, and for the app client it would be in the var/config/client_artifact_aliases.properties file.

The format for entries in these files is oldartifactid=newartifactId, here are two examples. Versions can be omitted on the left side but not the right. This can also specify explicit versions in the same format. Note that many of these examples have two lines for the "same" replacement. If all the dependencies specify the version, only need the line with the version specified in the left hand side. If all the dependencies omit the version, you only need the line without the version specified in the left hand side. At the moment whether or not versions are specified in geronimo dependencies is somewhat disorganized and random.

org.apache.geronimo.configs/j2ee-server//car=org.apache.geronimo.configs/j2ee-server/2.1/car

org.apache.geronimo.framework/j2ee-system//car=org.apache.geronimo.framework/client-system/2.1/car
org.apache.geronimo.framework/j2ee-security//car=org.apache.geronimo.configs/client-security/2.1/car
org.apache.geronimo.framework/j2ee-system/2.1/car=org.apache.geronimo.framework/client-system/2.1/car
org.apache.geronimo.configs/j2ee-server//car=org.apache.geronimo.configs/client/2.1/car
org.apache.geronimo.configs/transaction//car=org.apache.geronimo.configs/client-transaction/2.1/car
org.apache.geronimo.configs/transaction/2.1/car=org.apache.geronimo.configs/client-transaction/2.1/car
org.apache.geronimo.framework/j2ee-security/2.1/car=org.apache.geronimo.configs/client-security/2.1/car
org.apache.geronimo.configs/j2ee-server/2.1/car=org.apache.geronimo.configs/client/2.1/car

While you can modify these files by hand, a more recommended method is to deploy your applications as geronimo plugins and to install these aliases through the geronimo-plugin.xml descriptor, which is genereated when you build your plugin using maven. There are some examples Plugin infrastructure