Paul McMahan wrote:
On 1/12/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
If we do start shipping 8 (or more) different assemblies... which I
think is
crazy, then we probably don't want to hook them all up to the default
build,
as it will just cause it take longer and longer to run.
We really need to get plugins functional so that we can build one
assembly.
Please... :-)
AFAIK the plugin functionality already works sufficiently well to
support this approach. And the infrastructure should already be in
place as well since the plugin repository catalogs at
geronimo.apache.org point to maven repos where the Geronimo CARs get
published.
Granted we've only used plugins for installing applications so far and
really haven't tried using plugins to install or replace core jee5
services, so there may be missing functionality that needs our
attention.
Well, not core "jee5" services exactly ... but I did create plugins for
tomcat & jetty as well as their respective deployers and I could
successfully install those into micro-G (at least they worked a few
months ago). So we know this is possible.
Joe
Only way to know for sure is to identify each config that
should be provided as plugin, map out its dependencies, and add a
geronimo-plugin.xml to the CAR file that maven builds. Then update
the plugin catalog so when that CAR gets published to the maven repo
it will be installable as a plugin. There are several examples in
trunk/configs.
Best wishes,
Paul
