You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (Created) (JIRA)" <ji...@apache.org> on 2012/02/06 12:47:59 UTC

[jira] [Created] (DAEMON-240) Undocumented and inconsistent behaviour of multi-valued registry entries

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


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

        

[jira] [Issue Comment Edited] (DAEMON-240) Undocumented and inconsistent behaviour of multi-valued registry entries

Posted by "Mladen Turk (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DAEMON-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201358#comment-13201358 ] 

Mladen Turk edited comment on DAEMON-240 at 2/6/12 6:18 PM:
------------------------------------------------------------

Resolved by ensuring that --option rests the parser state.
1. In case --option ++option ... is used the resulting
   value will be overwritten with those command line (combined)
2. In case ++option ++option ... is used the resulting
   value will be appended to existing one.
3. ++option=a --option=b will cause that any options on
   the command line before last -- are dropped.
   No error or no warning is reported in that case.

                
      was (Author: mturk@apache.org):
    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

        

[jira] [Resolved] (DAEMON-240) Undocumented and inconsistent behaviour of multi-valued registry entries

Posted by "Mladen Turk (Resolved) (JIRA)" <ji...@apache.org>.
     [ 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