commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DAEMON-240) Undocumented and inconsistent behaviour of multi-valued registry entries
Date Mon, 06 Feb 2012 15:59:59 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mladen Turk resolved DAEMON-240.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.9

Resolved by disabling intermixing -- and ++ options on the same command line.
This means that either --option or any number of ++option can be used, but not together
                
> Undocumented and inconsistent behaviour of multi-valued registry entries
> ------------------------------------------------------------------------
>
>                 Key: DAEMON-240
>                 URL: https://issues.apache.org/jira/browse/DAEMON-240
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.8
>            Reporter: Sebb
>             Fix For: 1.0.9
>
>
> The behaviour of option processing for multi-valued registry entries is partly undocumented,
and inconsistent.
> --Option and ++Option are only documented in the context of a single invocation of procrun.
> The documentation should be updated to clarify that ++Option can be used in a separate
invocation of procrun (update service) to append values to the registry.
> ==
> The documentation implies that --Option resets the value.
> This is only true if the ++Option is not used at the same time - if the ++Option is used
anywhere on the command-line, then all the options are appended to any existing value in the
registry.
> The behaviour of mixed --Option and ++Option should either be fixed so that --Option
clears any existing settings, or the existing behaviour should be documented.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message