Cool! I wrote a (cough, cough) perl script to generate wiki markup for a table from the data in the configs/*/pom.xml files, and updated the wiki page with it. I then produced a merged table to compare existing pom descriptions to the ones I had entered. I'd like to get further input, store updated descriptions in the pom.xml description element, and then I think it makes sense to generate a page from the pom.xml data. There appear to be two attributes for each that would be nice to capture in doc: whether the module is initially started, and whether it should *never* be started. I wonder if any sort of attribute could be added for capturing this in pom.xml?
Ted Kirby On 10/2/07, David Jencks <[EMAIL PROTECTED]> wrote: > Nice! > > In trunk, the <description> element in the config's pom gets put into > the geronimo-plugin.xml description so it really needs to be > accurate. It would be great if we could generate future versions of > this page from the plugin catalog. Meanwhile it might be worthwhile > comparing the descriptions here with the descriptions in the trunk > configs' poms to make sure they are consistent and the most > informative wins :-) > > thanks! > david jencks > > On Oct 2, 2007, at 3:05 PM, Ted Kirby wrote: > > > I have added this wiki page > > http://cwiki.apache.org/GMOxDOC20/system-modules.html to list the > > modules that come with the (2.0.1) server, along with: > > > > 1. A brief description of what the module does > > 2. Is it started by default, or > > 3. Should it never be started? > > > > This is a first draft. I solicit feedback and encourage folks to > > update the page as appropriate. There are some modules with which I > > am not familiar. > > > > Ted Kirby > >
