This portlet lets you install or create Geronimo plugins.
- This can be used to install new features into a Geronimo server at runtime.

+
-

Install Geronimo Plugins

-
-

Choose a remote repository to inspect for available Geronimo plugins. The
-repository must have a geronimo-plugins.xml file in the root directory
-listing the available plugins in the repository.

-
-

You can also download running configurations from another Geronimo server
-just as if you're browsing and installing third-party plugins.
- If you want to point to a remote Geronimo server, enter a URL such as
-http://geronimo-server:8080/console/maven-repo/ and the enter
-the administrator username and password in the optional authentication fields.

Create Geronimo Plugin

+

+

+
-

Choose a configuration in the current Geronimo server to export as a Geronimo
- plugin. The configuration will be saved as a CAR file to your local filesystem.
- Note: at present, you must manually add a META-INF/geronimo-plugin.xml
- file to the CAR after you export it in order for it to be a valid plugin.

- The globally unique ID for this plugin. This is determined from
- the installation in the server you're exporting. This defines
- the version number for the plugin, so make sure it's correct.
+

-

Download Repositories:

+

:

- A list of repositories to check for any dependencies that need to be downloaded.
- This should be a list of one URL per line, with values such as
- http://geronimoplugins.com/repository/ and http://www.ibiblio.org/maven2/.
- Note that the repository this plugin is deployed to should typically be the first one listed.
+
+

-

Category:

+

:

- The category this plugin falls into. Plugins in the same category will
- be listed together. If this plugin is intended to be listed on
- geronimoplugins.com then you should use one of the category names there
- if any of them fit. Otherwise, you can select this freely, or according
- to the categories acceptable to the repository where you plan to post
- this.
+

-

Description:

+

:

- A description of this plugin. You should use plain text only, with
- blank lines to separate paragraphs.
+
+

-

Plugin URL:

+

:

- A URL to get more information about the plugin (e.g. the plugin home page).
+

-

Author:

+

:

- The author of the plug, which may be a person, company, open source project, etc.
+

-

License:

+

:

- The name of the license that this plugin is covered by. Ideally, it would
- be prefixed by the class of license, like "BSD -- (name)" or "GPL -- (name)".
+

- The Geronimo Version element is the version of geronimo that this plugin will
- be running on. It is a required element and take on values such as 2.0-SNAPSHOT
- and 2.0-M2
+

-

JVM Versions:

+

:

- An optional list of JVM version prefixes supported by this plugin. If no values
- are listed, the plugin can be installed in Geronimo running in any version of
- the JVM. Otherwise, list one acceptable JVM version perfix per line, like
- "1.4.2 \n 1.5 \n ..."
- (ideally, of course, this means you've actually tested the plugin with Geronimo
- on each JVM version listed here).
+
+

-

Dependencies:

+

:

-

- A list of JARs or other module IDs that this plugin depends on. These
- will be downloaded automatically when this plugin is installed. Normally
- you shouldn't change this list. However, you can move entries from the
- dependency list to the prerequisite list if the user must install the
- dependency manually before installing the plugin (e.g. for a database pool
- where a plugin wouldn't know what server to connect to).

- Each entry in this list should use the Unique ID format like is used for
- this plugin above. You may remove the version number if you'd like to
- work with any version of the dependency, though that may be risky. Each
- value should be on a separate line.
+

+

-

Obsoletes:

+

:

- A list of module IDs that this plugin replaces. Those plugins or
- modules will be removed when this one is installed. That may include
- previous versions of this plugin if you want installing it to "upgrade"
- rather than just offering an additional alternative. This should be a
- list with one module ID per line.
+
+

-

Prerequisite 1 ID:

+

:

- The module ID of a prerequisite for this plugin. This is a module that
- must be present in the server before the plugin can be installed. It
- may be something like a specific web container for a web application
- (geronimo/jetty/*/car) or something like a database pool or
- security realm that the user must install because the plugin author can't
- create a value that will be valid in the destination server. You may want
- to leave out as many segments of the module ID as possible in order to
- accomodate more users (e.g. */mypool/*/* rather than
- myapp/mypool/1.2/car).
+
+

-

Prerequisite 1 Type:

+

+
+ :

- A brief description of the type of prerequisite this is (for the benefit
- of the user). Examples could include Database Pool or
- Web Container.
+

-

Prereq 1 Description:

+

:

-

- A longer description of what the user needs to do to comply with this
- prerequisite (for example, instructions to set up a database pool listing
- the supported database products and telling the user where to find a script
- to initialize the database). This should be plain text with empty lines
- to separate paragraphs.
+

-

Prerequisite 2 ID:

+

:

- The module ID of a prerequisite for this plugin. This is a module that
- must be present in the server before the plugin can be installed. It
- may be something like a specific web container for a web application
- (geronimo/jetty/*/car) or something like a database pool or
- security realm that the user must install because the plugin author can't
- create a value that will be valid in the destination server. You may want
- to leave out as many segments of the module ID as possible in order to
- accomodate more users (e.g. */mypool/*/* rather than
- myapp/mypool/1.2/car).
+

-

Prerequisite 2 Type:

+

:

-

- A brief description of the type of prerequisite this is (for the benefit
- of the user). Examples could include Database Pool or
- Web Container.
+

-

Prereq 2 Description:

+

:

-

- A longer description of what the user needs to do to comply with this
- prerequisite (for example, instructions to set up a database pool listing
- the supported database products and telling the user where to find a script
- to initialize the database). This should be plain text with empty lines
- to separate paragraphs.
+

-

Prerequisite 3 ID:

+

>:

-

- The module ID of a prerequisite for this plugin. This is a module that
- must be present in the server before the plugin can be installed. It
- may be something like a specific web container for a web application
- (geronimo/jetty/*/car) or something like a database pool or
- security realm that the user must install because the plugin author can't
- create a value that will be valid in the destination server. You may want
- to leave out as many segments of the module ID as possible in order to
- accomodate more users (e.g. */mypool/*/* rather than
- myapp/mypool/1.2/car).
+

-

Prerequisite 3 Type:

+

:

-

- A brief description of the type of prerequisite this is (for the benefit
- of the user). Examples could include Database Pool or
- Web Container.
+

-

Prereq 3 Description:

+

:

-

- A longer description of what the user needs to do to comply with this
- prerequisite (for example, instructions to set up a database pool listing
- the supported database products and telling the user where to find a script
- to initialize the database). This should be plain text with empty lines
- to separate paragraphs.
+