Filter project contributors on the classpath

Is there any way to tweak/override/disable out-of-the-box @ProjectGenerationConfigurations ?

They are not loaded as auto-config-beans, but with spring.factories (via ProjectGenerator$CoreConfiguration). I can’t see any way to filter or customize these ?

I could try to provide my own ProjectGenerationInvoker bean (overriding the default bean from InitializrAutoConfiguration) and set up my own ProjectGenerator, but the interface requires me to construct a ProjectGenerationResult which has a package-private constructor.

Am I missing something or is this just not supported ? Yet ?

[wilkinsona]

I wonder if we could do this by allowing some control over the configuration class that’s registered when creating the project generation context:

https://github.com/spring-io/initializr/blob/e97233b1077407661660925e7b5383a7ae972736/initializr-generator/src/main/java/io/spring/initializr/generator/project/ProjectGenerator.java#L107-L109

CoreConfiguration does nothing other than pulling in an ImportSelector that imports all of the ProjectGenerationConfiguration classes registered in spring.factories. Allowing CoreConfiguration to be replaced would allow a different import selector to be used. This different selector could use spring.factories and filter the registrations or it could implement a different registration mechanism entirely.

There are a few different way that this customisation could be enabled. We could make it the responsibility of the ContextCustomizer, we could pass something in as a new type, or we could perhaps provide a protected method that can be overridden.

[snicoll]

perhaps contributors can be conditionally enabled via ConditionalOnProperty annotations, much like how actuator endpoints or health actuator contributors are turned on/off. This will allow control over each ProjectContributor and is not drastic enough to block or cause trouble for future enhancements. What do you think?

We thought of that as it would be a natural move with regards to what you can find in Spring Boot. We’ve ruled it out with the current infrastructure as we don’t have any way to debug this (similar to the auto-configuration report and the actuator endpoint). It is also something that can be a bit involved if you want to get this done per request or globally.

The initializr-generator-spring would only autoconfigure such apis (instead of defining them + autoconfigure them).

This is a valid idea but I am not keen to do such a split at this level. The module with the @ProjectGenerationConfiguration would be a shell and the surface area is too small to warrant such work IMO. I’d like to explore how a ProjectGenerator can filter those upfront but I haven’t had the time to look at a solution yet, sorry.