You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/09/02 09:31:19 UTC

[jira] Assigned: (GERONIMO-3330) plugin schema for reducing redundancy in the catalog

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

David Jencks reassigned GERONIMO-3330:
--------------------------------------

    Assignee: David Jencks  (was: Paul McMahan)

> 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.