See https://github.com/spring-projects/spring-framework/issues/13410#issuecomment-1967596598

Comment From: ballista01

Hi @wilkinsona I'd like to contribute to the issue. However, I'm facing some issues. Right now, the spring-boot master branch has a dependency springFrameworkVersion=6.1.5 https://github.com/spring-projects/spring-boot/blob/af0353ddd3af37cd36cfb84da9cc7f4c085ff50b/gradle.properties#L17, according to the comment you referred to, the @Bean(bootstrap=BACKGROUND) feature is introduced in spring framework 6.2.0. I tried to change the springboot's dependency to the spring framework to springFrameworkVersion=6.2.0-SNAPSHOT but got the following errors:

(base) wiz@wiz-ubuntu:~/Projects/uni/hands_on_refactor/spring-boot$ ./gradlew build -x test --refresh-dependencies

> Task :spring-boot-project:spring-boot-test:compileJava FAILED
/home/wiz/Projects/uni/hands_on_refactor/spring-boot/spring-boot-project/spring-boot-test/src/main/java/org/springframework/boot/test/web/htmlunit/webdriver/LocalHostWebConnectionHtmlUnitDriver.java:43: error: cannot access BrowserVersion
                super(enableJavascript);
                     ^
  class file for org.htmlunit.BrowserVersion not found
/home/wiz/Projects/uni/hands_on_refactor/spring-boot/spring-boot-project/spring-boot-test/src/main/java/org/springframework/boot/test/web/htmlunit/webdriver/LocalHostWebConnectionHtmlUnitDriver.java:49: error: no suitable constructor found for WebConnectionHtmlUnitDriver(com.gargoylesoftware.htmlunit.BrowserVersion)
                super(browserVersion);
                ^
    constructor WebConnectionHtmlUnitDriver.WebConnectionHtmlUnitDriver(org.htmlunit.BrowserVersion) is not applicable
      (argument mismatch; com.gargoylesoftware.htmlunit.BrowserVersion cannot be converted to org.htmlunit.BrowserVersion)
    constructor WebConnectionHtmlUnitDriver.WebConnectionHtmlUnitDriver(boolean) is not applicable
      (argument mismatch; com.gargoylesoftware.htmlunit.BrowserVersion cannot be converted to boolean)
    constructor WebConnectionHtmlUnitDriver.WebConnectionHtmlUnitDriver(Capabilities) is not applicable
      (argument mismatch; com.gargoylesoftware.htmlunit.BrowserVersion cannot be converted to Capabilities)
Note: Some messages have been simplified; recompile with -Xdiags:verbose to get full output
2 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':spring-boot-project:spring-boot-test:compileJava'.
> Compilation failed; see the compiler error output for details.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.6.4/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 13s
1225 actionable tasks: 154 executed, 1071 up-to-date

Is the current springboot version not ready for spring framework 6.2.0 yet? If so, should I develop this enhancement in spring framework?

Comment From: wilkinsona

Thanks for taking a look, @ballista01. We won't be able to work on this issue until we've started developing Spring Boot 3.4 and have upgraded to a Spring Framework 6.2 milestone or snapshot. This won't happen until some time after Spring Boot 3.3's release in May.

Comment From: YongGoose

@wilkinsona

I’m interested in this issue. May I ask if I can contribute to it?

Comment From: wilkinsona

Thanks for the offer, @YongGoose, but I'm not sure we know exactly how to implement this yet. Reading https://github.com/spring-projects/spring-framework/issues/13410#issuecomment-1967596598 again, there's the possibility of aliasing the application task executor to bootstrapExecutor but also perhaps a need to allow a boostrap-specific executor to be configured. We'll have to sync up with the Framework team to see if both of these options still make sense and then figure out how we might implement them in Boot.

Comment From: YongGoose

@wilkinsona

I understand. I would be grateful if you could let me know once the implementation direction is determined after discussing with the Spring team. 😁

ps. Additionally, there is another issue I am interested in. Would it be possible for me to contribute to this issue? - https://github.com/spring-projects/spring-boot/issues/36953

Comment From: wilkinsona

I think that one probably needs some design work too, unfortunately. Reading through the comments there still seems to be quite a bit that's undecided.