Glue property #2330
|
Thanks for answering my question about JSpecify support the other day. Much appreciated! I have one more question in regard to Cucumber 8.x. We used to specify the location of glue code as follows: @ConfigurationParameter(key = GLUE_PROPERTY_NAME, value = "com.foo.bar")I noticed a lot of warnings during Maven build complaining that this was inefficient. There seem to be a few different ways of specifying the glue code now, such as |
Replies: 1 comment 1 reply
|
Cucumber has to load the classes it scans for step definitions and other glue code. The class loading is quite slow. You get this warning because Cucumber noticed that it scans a lot of classes that don't contain anything useful. Which classes get scanned is controlled by 3 properties. The What the best combination is depends on your project structure. You can use If that's not the case you can either change If your glue classes are located in multiple different packages, but they do follow a common naming structure you could keep If you don't have a naming pattern and you glue classes are mixed with other classes you also turn off the warning. That's perfectly fine too. The warning implicitly assumes there something that can be optimized. This doesn't have to be the case. |
Cucumber has to load the classes it scans for step definitions and other glue code. The class loading is quite slow. You get this warning because Cucumber noticed that it scans a lot of classes that don't contain anything useful.
Which classes get scanned is controlled by 3 properties. The
cucumber.glue,cucumber.glue.classesandcucumber.glue.{included,excluded}-class-name-patterncomplement each other.What the best combination is depends on your project structure.
You can use
cucumber.glueto specify the general location. And if that package and its subpackaces mostly contain classes with step definitions or other glue code you shouldn't see a warning.If that's not the case you can ei…