-
-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spring-boot-cucumber broken because it depends only on the spring-server module #5104
Comments
It is a workaround for fixing #4153 Probably this fix is not perfect but it was the easiest for now. I don't know if spring-boot-cucumber works with webflux. We should test it and if it doesn't work, we can simply change the dependency: spring-boot-cucumber should depend on spring-mvc-server Another solution would be to rename spring-boot-mvc to spring-boot-mvc-empty so it's totally clear this module is just an empty module |
Anyway, thanks for giving a try to this project @bagnier |
At first, thank you folks for this useful and ambitious project 💪 ! Thank you @pascalgrimaud for pointing me to this bug report and giving me a better understanding of the context. I will refocus this report around spring-boot-cucumber. I tried these configurations :
If the goal of this project is to provide a working software for any valid configuration as selected in the tool, then this issue is a bug. The spring-boot-cucumber module can be enabled without working dependencies. my 2 cents:
|
Cc @DamnClin as he's the one who implemented the Cucumber module |
Apply spring-boot-mvc module does not provide the spring-boot-starter-web Maven dependency.
Apply spring-boot-tomcat module does. This seems to me a little bit misleading.
For instance, the spring-boot-cucumber module can be broken because it depends only on the spring-server module.
The Maven dependencies are broken when:
The text was updated successfully, but these errors were encountered: