You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2016/12/09 09:40:58 UTC
[jira] [Resolved] (OAK-5255) Flags in the oak-upgrade should allow
to set boolean parameter value
[ https://issues.apache.org/jira/browse/OAK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomek Rękawek resolved OAK-5255.
--------------------------------
Resolution: Won't Fix
> Flags in the oak-upgrade should allow to set boolean parameter value
> --------------------------------------------------------------------
>
> Key: OAK-5255
> URL: https://issues.apache.org/jira/browse/OAK-5255
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
> Affects Versions: 1.4.10, 1.5.15
> Reporter: Tomek Rękawek
> Fix For: 1.6
>
> Attachments: OAK-5255.patch
>
>
> There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It seems that these flags accepts parameters (passed with =) but their value is ignored. As a result specifying:
> * {{\-\-copy\-binaries}}
> * {{\-\-copy\-binaries=true}}
> * {{\-\-copy\-binaries=false}}
> * {{\-\-copy\-binaries=xyz}}
> has the same effect. On the other hand, the only way to unset this flag is skipping the parameter at all.
> We should change this behaviour. The argument may be still optional, but oak-upgrade should only accept boolean values and interpret them accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)