You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Bjarne Boström (JIRA)" <ji...@apache.org> on 2015/04/10 14:39:13 UTC
[jira] [Created] (CONFIGURATION-598) There are 2 different
ConfigurationBuilder interfaces
Bjarne Boström created CONFIGURATION-598:
--------------------------------------------
Summary: There are 2 different ConfigurationBuilder interfaces
Key: CONFIGURATION-598
URL: https://issues.apache.org/jira/browse/CONFIGURATION-598
Project: Commons Configuration
Issue Type: Bug
Affects Versions: 2.0-alpha1
Reporter: Bjarne Boström
Priority: Minor
Fix For: 2.0
(This is my first time entering a bug here; at least searching with ConfigurationBuilder here did not bring any relevant issues so I wanted to post this)
There are 2 different ConfigurationBuilder interfaces:
one is {{org.apache.commons.configuration2.ConfigurationBuilder}} and other is
{{org.apache.commons.configuration2.builder.ConfigurationBuilder}}
The base package has
{code}
Configuration getConfiguration()
{code}
while the builder package has
{code}
T getConfiguration()
{code}
and the (<T extends Configuration> as generic parameter in the interface)
I assume this is a bug, since nothing implements the base package one and all ConfigurationBuilder implementations implement the one in the builder subpackage. It is at least confusing in case the base package one is intended just for clients to implement. Also documentation points to the builder package one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)