Wrong semantic for immutable @ConfigurationProperties contributed via @Import

[mpalourdio]

Hello,

As of SB 2.2.0.M5, the changelog states that @ConfigurationProperties-annotated types are no longer scanned in slice tests unless imported explicitly. This restores the behaviour that slice tests should only scan what is described in the documentation.

When an immutable @ConfigurationProperties is imported in a test slice, and the constructor parameters are not beans (ex : strings), the test fail.

As it's not that easy to describe, I have done a repository that reproduces the issue : https://github.com/mpalourdio/demorepro . Please run the single test to see it fail.

In order to make it work with SB 2.0.0.M4, remove the @Import in the test class, and change the SB version in pom.xml to target SB 2.0.0.M4. The test will succeed.

Thanks by advance, and let me know if you need more information.

[mpalourdio]

Replacing @Import by @EnableConfigurationProperties fixes the issue.

@EnableConfigurationProperties makes more sense of course... I was mislead by the wording of the changelog I think.

[snicoll]

@mpalourdio Thanks for reporting it. It would be nice if @Import would work as well or that we at least make this crystal clear in the documentation.

What bugs me is that if it wasn't immutable it would just work and I'd like users don't have to care about that.

[mpalourdio]

Thanks for feedback. My bad, just deleted the repository as I thought the intended behaviour was EnableConfigurationProperties.

Do you want me to reproduce another sample ?

[snicoll]

No, I have one. Thank you.

[mpalourdio]

The repository has been restored!