On Mon, 15 Mar 2004, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > Is it recommended that the Gump Descriptor is in Gump or the > Project??
Depends on what you do with it. Forrest and Cocoon have the descriptors inside their modules since they use the descriptors for other things they do during their normal build AFAIU. Both descriptors contain a bunch of extra information that is ignored by Gump. For most Apache projects it doesn't make too much sense to keep the descriptors inside a project specific module since you just limit the number of hands that can fix it. Something that isn't widely understood is that every Apache committer is a Gump committer, so the number of people with access to the gump module is a superset of those with access to any project specific module. My recommendation would be to put the descriptors into the gump module, unless you need them for your own. One reason why the Avalon descriptors are in Avalon modules (they've moved back and force a few times) has been, that whoever moved them there hoped the avalon community would take ownership of them. The avalon build system is complex and it really takes somebody from the Avalon community who understands the system to get the descriptors right. If the descriptors get moved to the gump module and nobody cares for them, we haven't won anything. If the only people who can access it are Avalon people, there may be a better chance to actually get one of you guys involved in fixing it (thanks a lot for that, Niclas!!). Cheers Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]