Human Readable Name:
A human-readable name that will be displayed for this plugin.
Unique ID:
${configId}
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)".
Open Source:
Check this box if the license is an OSI-approved open source license
(see http://www.opensource.org/licenses/index.php ).
Geronimo Versions:
An optional list of Geronimo versions supported by this plugin. If no values
are listed, the plugin can be installed in any version of Geronimo. Otherwise,
list one acceptable Geronimo version per line, like
"1.1 \n 1.1.1 \n 1.1.2 \n ..."
(ideally, of course, this means you've actually tested the plugin with each
Geronimo version listed here).
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).
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.