It seems to make sense just to have the entry in the plugin catalog if no module-id exists, as I cannot really think of anything else that we have for this type of plugin other than the geronimo-plugin.xml file. If that is the case, we only need c-m-p to update the plugin catalog. When the plugin catalog is updated, a user can select the plugin group out of a plugin catalog, instead of individual plugins, which is a nice feature for our users to do plugin installation.
Lin On Fri, Aug 22, 2008 at 3:19 AM, David Jencks <[EMAIL PROTECTED]> wrote: > I'm not sure how much sense it makes to use the c-m-p to generate a > geronimo-plugin.xml with no moduleId. IIRC the original idea (from Aaron) > was to just have the entry in the plugin catalog. Without a moduleId you > can't put it in the maven repo (IMO). So, maybe we do want a moduleId but > make it so nothing gets into any config.xml??? > > I've started to wonder if we should distribute the geronimo-plugin.xml files > as attached artifacts with a geronimo-plugin classifier so they are more > readily available as plain files. > > still thinking..... > david jencks
