[
https://issues.apache.org/jira/browse/CONFIGURATION-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542531#comment-14542531
]
Oliver Heger commented on CONFIGURATION-601:
--------------------------------------------
Indeed, we do not honer string literals. I fear this will not be easy to
support, it comes with a whole bunch of follow-up issues, e.g. support for
different quote character, escaping, line continuation, etc.
In your specific case, you are hit by the comma character being interpreted as
list delimiter. The user guide describes multiple approaches to work around
this problem:
*
http://commons.apache.org/proper/commons-configuration/userguide_v1.10/howto_basicfeatures.html#List_handling
*
http://commons.apache.org/proper/commons-configuration/userguide_v1.10/howto_properties.html#Lists_and_arrays
*
http://commons.apache.org/proper/commons-configuration/userguide_v1.10/howto_properties.html#Special_Characters_and_Escaping
Note that in the upcoming version 2.0 the behavior of list delimiter parsing
has changed. It is then disabled by default (due to the many problems it has
created) and has to be explicitly enabled if desired.
> honor values that are string literals
> -------------------------------------
>
> Key: CONFIGURATION-601
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-601
> Project: Commons Configuration
> Issue Type: Bug
> Components: Interpolation
> Affects Versions: 1.9
> Reporter: Kalen Krempely
> Priority: Minor
>
> Parsing the following file, does not honor keys that are string literals such
> as:
> some_key = "hi there, would you like to (play with me)"
> yields:
> key: some_key
> val: "hi there
> rather than the expected result of:
> key: some_key
> val: "hi there, would you like to (play with me)"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)