You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2024/06/03 18:53:00 UTC
[jira] [Commented] (CONFIGURATION-847) Property with an empty string value are not processed in the current main (2.11.0-snapshot)
[ https://issues.apache.org/jira/browse/CONFIGURATION-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851778#comment-17851778 ]
Gary D. Gregory commented on CONFIGURATION-847:
-----------------------------------------------
PR merged to git master. Build in [https://repository.apache.org/content/repositories/snapshots/]
> Property with an empty string value are not processed in the current main (2.11.0-snapshot)
> -------------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-847
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-847
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: Nightly Builds
> Reporter: Andrea Bollini
> Assignee: Gary D. Gregory
> Priority: Critical
> Fix For: 2.11.0
>
>
> I hit a side effect of the https://issues.apache.org/jira/browse/CONFIGURATION-846 recently solved.
> {{Assuming that we have a property file as configuration source like that}}
> {{test.empty.property =}}
>
> and that we will try to inject such property in a spring bean
> {{@Value("${test.empty.property"})}}
> {{private String emptyValue;}}
> {{ we will get an exception like: BeanDefinitionStore Invalid bean definition ... Could not resolve placeholder}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)