geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3330) plugin schema for reducing redundancy in the catalog
Date Tue, 07 Aug 2007 15:43:59 GMT

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

Paul McMahan commented on GERONIMO-3330:
----------------------------------------

capturing a couple of comments on this JIRA provided by David Jencks during a conversation
at OSCON:
* the <plugin-module> element should be renamed to something else like perhaps <plugin-artifact>.
 using "plugin-module" for the name could be misleading since it implies that the information
provided within it is a composite part of the overall plugin when actually it is an stand
alone entity that is to be treated as separate and disjoint from its sibling elements
* smooshing the group, artifactid, version, and type into a <module-id> element by using
'/' as the delimiter is inflexible and not consistent with maven.  the information about a
plugin module should instead be broken into <group>, <artifactid>, <version>,
and <type> elements

> 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: Paul McMahan
>         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