commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONFIGURATION-564) PropertiesReader.doParseProperty() version 1.8+ not backward compatible
Date Thu, 30 Jan 2014 20:34:09 GMT

    [ https://issues.apache.org/jira/browse/CONFIGURATION-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887022#comment-13887022
] 

Oliver Heger commented on CONFIGURATION-564:
--------------------------------------------

This looks like a regression then. Any chance you can provide a unit test or even a patch?

> PropertiesReader.doParseProperty() version 1.8+ not backward compatible
> -----------------------------------------------------------------------
>
>                 Key: CONFIGURATION-564
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-564
>             Project: Commons Configuration
>          Issue Type: Bug
>          Components: Format
>    Affects Versions: 1.8, 1.9, 1.10
>            Reporter: pascal gehl
>
> We have a legacy application using a library with properties configuration files where
some properties are only keys; Example:
> property.key
> instead of 
> property.key=value or property.key=
> Until version 1.7 those properties where present with no value in our CompositeConfiguration
instance.
> Starting with version 1.8 (introducing a private not overridable regex pattern) those
properties are now left out of our application configuration.
> Since we don't own the lib we can't move to latest version of commons-configuration and
are stuck with version 1.7



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message