[
https://issues.apache.org/jira/browse/KARAF-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826105#comment-16826105
]
ASF GitHub Bot commented on KARAF-6256:
---------------------------------------
JiriOndrusek commented on pull request #821: [KARAF-6256] Parsing string arrays
in org.apache.karaf.management.cfg…
URL: https://github.com/apache/karaf/pull/821
… doesn't ignore spaces
Issue: https://issues.apache.org/jira/browse/KARAF-6256
Small fix, which allows to define properties with spaces after comma
(enabledProtocols=TLSv1.2, TLSv1.1 would be parsed as "TLSv1.2" and "TLSv1.1")
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Parsing string arrays in org.apache.karaf.management.cfg doesn't ignore spaces
> ------------------------------------------------------------------------------
>
> Key: KARAF-6256
> URL: https://issues.apache.org/jira/browse/KARAF-6256
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.3.0
> Reporter: Jiri Ondrusek
> Priority: Major
>
> I can define "string array" properties in org.apache.karaf.management.cfg
> (e.g. enabledProtocols)
> If I define enabledProtocols=*TLSv1.2,TLSv1.1* everything is right. (Parsed
> values are *"TLSv1.2"* and *"TLSv1.1"*)
> But when I define enabledProtocols=*TLSv1.2, TLSv1.1*, array is parsed as
> *"TLSv1.2"* and *" TLSv1.1"*, which is wrong.
> Correct behavior: white spaces in "string arrays" should be ignored.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
