-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Deprecate Spring context configuration by more than one class #1259
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think your editor is configured to use tabs instead of spaces.
0d0baef
to
83da61a
Compare
Removed all tabs. |
Your step definitions no longer have to extend from that class. You can either pick any one of your step definition classes and put the spring configuration on that one. Or you can use a dedicated class like |
The example project is your best guess at the moment. https://github.com/cucumber/cucumber-jvm/tree/master/examples/spring-txn |
Thanks. I've found it in the meantime and I removed my previous question, but I guess it's good you replied if anyone else wonders about the same thing again. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Deprecate Spring context configuration by more than one class
Details
Print a warning if more than one glue class that attempts to configure the Spring context is found (that is have a
@ContextConfiguration
or@ContextHierarcy
annotation.Motivation and Context
We have decided to only allow one glue class to configure the Spring context, as this is a non-backward compatible change, it will be introduced in v3.0.0 (#1246). Until then a deprecation warning should be printed.
How Has This Been Tested?
The automated test suite has been updated to verify this behavior.
Types of changes
Checklist: