Application does not start due to two bean instances of org.springframework.plugin.core.PluginRegistry (Follow-up)

As explained in the last comment of #966 , an application using spring-hateoas-1.0.0 does not start if the bean factory is setup in a way that the ParameterNameDiscoverer is null or an alternative implementation.

The reason is that when autowiring of PluginRegistry into the bean _relProvider it finds two candidates and choosing one soley relies on the constructor argument name (same in EntityLinksConfigurationwhere the other instance of PluginRegistry is created.)

This could be easily resolved by using @Qualifier annotations and named beans.

[chanchal99999]

Add into SwaggerConfig @Bean public LinkDiscoverers discovers() {

	List<LinkDiscoverer> plugins = new ArrayList<>();
	plugins.add(new CollectionJsonLinkDiscoverer());
	return new LinkDiscoverers(SimplePluginRegistry.create(plugins));
	
}

[mgargadennec]

Same here after migration to Spring-Boot 2.2.0.RELEASE.