Serenity splits io.cucumber packages

[mpkorstanje]

What happened?

Serenity splits io.cucumber packages.

Currently this leads to the occasional breakage for users of Serenity when I change or remove an internal API (example: cucumber/cucumber-jvm#3076). In the future once cucumber/cucumber-jvm#2962 is implemented this will break permanently due to the module system.

What did you expect to happen?

I would expect Serenity:

1. To not shadow io.cucumber under any circumstance.
2. Create a feature request against Cucumber for things that can't be done without shadowing.

[mpkorstanje]

@wakaleo

1. On a quick count there is a about $1400+ per month available from Tidelift for the maintenance of serenity-bdd. Details at: https://tidelift.com/lifter/search?q=net.serenity-bdd

2. The link presented on Github to your consultancy when creating an issue against serenity-core is broken. Currently https://serenity-dojo.com/serenity-bdd-enterprise-support returns 404s.

3. Your email reachme@wakaleo.com doesn't work either.

[wakaleo]

HI @mpkorstanje,

Thanks for letting me know about the broken link. The best email to ask for support requests is support@serenity-dojo.com. It seems there was a glitch in the Tidelift setup which should be resolved soon, but if you would like to reach out via email I can update you on the available Serenity Dojo support packages.