geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3330) plugin schema for reducing redundancy in the catalog
Date Mon, 03 Sep 2007 18:01:06 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524564
] 

David Jencks commented on GERONIMO-3330:
----------------------------------------

Most of this is done in rev 572395 but the cli and console plugin installers need a lot more
work.  Also all the car poms need to be fixed up so the generated geronimo-plugin.xml is reasonably
accurate.

> plugin schema for reducing redundancy in the catalog
> ----------------------------------------------------
>
>                 Key: GERONIMO-3330
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3330
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Plugins
>    Affects Versions: 2.1
>            Reporter: Paul McMahan
>            Assignee: David Jencks
>         Attachments: plugins-1.2.xsd
>
>
> GERONIMO-2757 introduced some changes to the geronimo plugin schema to allow more flexibility
with specifying the geronimo version for a plugin.  Further refinements to the schema can
provide even greater flexibility and reduce the redundancy and complexity in  plugin catalogs.
  Grouping the version and container sensitive part of the plugin data into elements within
<geronimo-plugin> will help avoid separate catalog entries for tomcat and jetty compatible
plugins, and also associate the version sensitive data closer to the geronimo-version element.
  I will attach a schema that demonstrates how this can be implemented.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message