karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KARAF-2400) config:prop* command's '-b' option not as documented
Date Wed, 20 Nov 2013 12:17:36 GMT

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

Christian Schneider updated KARAF-2400:
---------------------------------------

    Fix Version/s:     (was: 3.0.0)

> config:prop* command's '-b' option not as documented
> ----------------------------------------------------
>
>                 Key: KARAF-2400
>                 URL: https://issues.apache.org/jira/browse/KARAF-2400
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-documentation
>    Affects Versions: 2.3.1, 2.3.3
>         Environment: Windows 7 + JDK 1.6
>            Reporter: Opher Shachar
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: 2.4.0, 2.3.4
>
>
> The [documentation|http://karaf.apache.org/manual/latest-2.3.x/commands/commands.html]
describes *{{config:prop\*}}* commands as having a _-b_ option to bypass storage.
> But actually this _-b_ option *only has affect* when combined with _*-p*_ option, otherwise
it is the _-b_ option to the {{config:update}} command that determines if changes are persisted
to disk.
> As example:{code}
> karaf@root> cat etc/org.ops4j.pax.logging.cfg|grep foo
> karaf@root> config:edit org.ops4j.pax.logging
> karaf@root> config:propappend -b log4j.logger.foo.bar DEBUG
> karaf@root> config:update
> karaf@root> cat etc/org.ops4j.pax.logging.cfg|grep foo
> log4j.logger.foo.bar = DEBUG
> {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message