[TAMAYA-77] Clearify the usage of the ConfigurationContextBuilder

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.1-incubating
• Fix Version/s: 0.1-incubating
• Component/s: Core
• Labels: spi
• Assignee: Oliver B. Fischer
• Reporter: Oliver B. Fischer
• Created: 25/Apr/15 21:57
• Updated: 24/Apr/19 20:00
• Resolved: 05/Aug/15 21:30

Description

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?

Issue Links

• links to: GitHub Pull Request #47

Sub-Tasks

• Adapt the jQAssistant rules for services and service providers: Resolved