Extract auto-config into separate module #329
Milestone
Comments
jvalkeal
added a commit
to jvalkeal/spring-shell
that referenced
this issue
Dec 19, 2021
- Create separate spring-shell-autoconfigure and keep all autoconfig features there. - Fixes spring-projects#329
Merged
jvalkeal
added a commit
to jvalkeal/spring-shell
that referenced
this issue
Dec 19, 2021
- Create separate spring-shell-autoconfigure and keep all autoconfig features there. - Fixes spring-projects#329
jvalkeal
added a commit
that referenced
this issue
Dec 19, 2021
- Create separate spring-shell-autoconfigure and keep all autoconfig features there. - Fixes #329
jvalkeal
added a commit
that referenced
this issue
Dec 24, 2021
- Lot of rework to move better model to work around bean cycles - Remove use of @lazy - Move StandardAPIAutoConfiguration to autoconfig package - Remove some of a direct ObjectProvider use in constructors - Adds spring-native support with most of a things working out of a box - Relates #324 - Relates #329 - Relates #323
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a various auto-config classes in a modules which is an anti pattern
as it's there forcefully feeding those into a user. Create a module
spring-shell-autoconfigureand keep all boot related classes there so thatuser can mix and match dependencies depending on what's needed.
The text was updated successfully, but these errors were encountered: