piyush

@rishabhpoddar, is the issue still relevant? Can I take it up?

@Romani, is the refactoring and pitest removal part of the same isssue? I was going through the code of `DefaultLogger.java` and I see a lot of overloaded constructors. One standard...

> It is refactoring. Pitest should not be increased. > > > One standard approach would be to use a builder pattern > > This is API class , we...

> Try update single class and send PR for review Sure

When you talk about improving the exception message using step definitions, are you asking to verify the step definitions if they are a part of classpath? I have added a...

> The exception I originally mentioned typically happens when a user tries to use cucumber without either `cucumber-java` or `cucumber-java8` as a dependency. These dependencies contain the `JavaBackend` and `Java8Backend`...

> Aside from being factually incorrect, the message you propose is rather woolly and mentions (to the user) irrelevant implementation details. > > Out of curiosity, did you just ask...

Yes, I am from India. Thank you for such warm gesture. I did as mentioned starting with Java-Skeleton repository. So, without removing the cucumber-java, it already had some issues with...

``` Before All/After All failed io.cucumber.core.exception.CompositeCucumberException: There were 2 exceptions. The details are in the stacktrace below. at io.cucumber.core.runtime.RethrowingThrowableCollector.getThrowable(RethrowingThrowableCollector.java:57) at io.cucumber.core.runtime.CucumberExecutionContext.getThrowable(CucumberExecutionContext.java:102) at io.cucumber.core.runtime.CucumberExecutionContext.finishTestRun(CucumberExecutionContext.java:97) at io.cucumber.core.runtime.Runtime.run(Runtime.java:89) at io.cucumber.core.cli.Main.run(Main.java:87) at io.cucumber.core.cli.Main.main(Main.java:30) Suppressed:...

No backends were found. Cucumber relies on backend module to run steps. It appears to be missing from your CLASSPATH. Please make sure you have a backend module in your...