bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Martin <gary.mar...@wandisco.com>
Subject Re: [Apache Bloodhound] #516: No ticket view permission for nightly build demo configuration
Date Wed, 08 May 2013 17:17:12 GMT
On 08/05/13 18:06, Olemis Lang wrote:
> On 5/8/13, Gary Martin <gary.martin@wandisco.com> wrote:
>> On 08/05/13 16:15, Olemis Lang wrote:
>>> On 5/8/13, Gary Martin <gary.martin@wandisco.com> wrote:
> [...]
>>>> If it is, how does that allow me to add a resolution enum to a product,
>>>> for example?
>>>>
>>> Product prefix = test
>>>
>>> {{{
>>> #!sh
>>>
> [...]
>>> Trac [/path/to/trac/env]> product admin test resolution add custom
>>> Trac [/path/to/trac/env]> product admin test resolution list
>>>
> [...]
>>> }}}
>>>
>> Fair enough. I didn't spot that in the list of commands. I obviously was
>> not looking hard enough.
>>
> JFTR the second part of the command (i.e. resolution ...) is
> «re-dispatched» to the target admin command handler but in product
> scope . Therefore help msg is generic Supported command list might be
> even different to global cmd list given the fact that component
> enable/disable rules in product scope might be different to global
> list .
>
> Therefore maybe it's ok to improve product admin cmd help docs ... or
> just add a reference to a wiki page clarifying its usage .
>

It seems a reasonable solution. I might expect something like "product 
admin [product] help" or "product help admin [product]" for the purpose 
of listing the available product admin commands.

Cheers,
     Gary

Mime
View raw message