geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder" <>
Subject Re: Using a Repository with Geronimo Plugins
Date Mon, 31 Jul 2006 14:40:27 GMT
Is the situation that you have a plugin and are just trying to install
it?  If so...

The normal "Deploy New" screen won't deploy plugins properly.  You can
use the Plugin Create/Install screen or the command-line deploy tool.
More on these in a minute.

If your machine is behind a proxy, can you use the JVM startup
argument to provide the proxy server?  I'm not sure what the name of
the setting is, but I've seen it before -- something like
-Dhttp.proxy.server=hostname -Dhttp.proxy.port=8080.  Can you try to
identify and use this setting and report back whether it works for

If you want to add a new repository to the plugin repository list, you
currently need to add it in config.xml -- there is a Jira to correct
this (adding the ability to add repositories via the console).  In the
mean time, make sure the server is down, and look for <attribute
name="userRepositories">[]</attribute> in the config.xml and add a
comma-separated list of URLs between the brackets.  FYI, you should be
able to use a file:/ URL to access your local repository (you don't
need to run it through a web server).

However, the repository must have a geronimo-plugins.xml file in the
root that is basically the consolidation of the geronimo-plugin.xml
files for all the plugins in the repository (it uses a different root
tag, but includes all the plugin metadata as-is).  This is used so the
client doesn't need to crawl the whole repository in order to identify
available plugins.  The format of this is described in the plugin
schema at and
for an example, you can see

Finally, if you have a plugin file, you can install it at the command
line using the "install-plugin" command for the deploy tool.  That
command will download dependencies from whatever repositories are
listed in your geronimo-plugin.xml file for the plugin you're
installing, and you don't typically need the top-level metadata file
since you're not browsing.  So you could save a lot of steps by just
putting the file:/ URL in your plugin metadata and installing the
plugin with the command-line tool.


On 7/31/06, Dennis Cartier <> wrote:
> I decided to try out the plugin packager and deployer in G 1.1
> From what I can glean, the new capabilities of G 1.1 should allow
> Geronimo to download applications and dependencies from a local
> repository just using a plugin created from an existing  deployment.
> Unfortunately I have been unable to get this to work and just need a
> push to get me over the hump.
> What I have done so far:
> 1. Exposed my local repository through Apache to be accessed over HTTP
> 2. Included the URL for the repository when creating the plugin as
> indicated in the 'Create and Install Plugins' page.
> I am not sure of the format of the mentioned 'geronimo-plugins.xml'
> file that is required to be in the root of the repository. In any
> case, I do not see any attempt to access the repository when the
> plugin is deployed. This may be because I have been trying to deploy
> the plugin through the 'Deploy New' under Applications. I suspect that
> the deployment should be done under the plugin page, but I have found
> that there does not appear to be anyway to edit the available
> repositories, and if you are behind a firewall that requires a proxy
> server to be used, then the repository interface is completely
> non-functional.
> Can anyone give me a push in the right direction?
> Thanks
> Dennis
> --
> "The music business is a cruel and shallow money trench, a long
> plastic hallway where thieves and pimps run free, and good men die
> like dogs. There's also a negative side. "
> Hunter S. Thompson, US journalist (1939 – 2005)

View raw message