[jira] [Commented] (TAMAYA-77) Clearify the usage of the ConfigurationContextBuilder

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on TAMAYA-77:
-------------------------------------------------------

Commit 767f65a13074be58fd89ccd1d3c3eab1b255ef0a in incubator-tamaya's branch refs/heads/master from P. Ottlinger
[ https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;h=767f65a ]

Merge pull request #47 from apache/more_sonar_updates

TAMAYA-77: Change sonar config to use mvn style for analysis

> Clearify the usage of the ConfigurationContextBuilder
> -----------------------------------------------------
>
>                 Key: TAMAYA-77
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-77
>             Project: Tamaya
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 0.1-incubating
>            Reporter: Oliver B. Fischer
>            Assignee: Oliver B. Fischer
>            Priority: Major
>              Labels: spi
>             Fix For: 0.1-incubating
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This issue is a reminder to discuss the usage of the ConfigururationContextBuilder.
> While analyzing our service providers I recognized that the {{DefaultConfigurationContextBuilder}} is not treated like a service provider. Instead of accessing it via the usual SPI meachnism simply a new instance is created. Furthermore {{DefaultConfigurationContextBuilder}} is the  only implementation of {{ConfigurationContextBuilder}}.
> We should discuss:
> - could be there more than one implementation of {{ConfigurationContextBuilder}}?
> - If no, can we remove the {{ConfigurationContextBuilder}} interface from our API?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)