Use io.cucumber.<package-name> for internal classes

[mpkorstanje]

Summary

Introduces the io.cucumber.<package-name> structure for all internal classes.

Motivation and Context

With this PR I hope to achieve a couple of aims.

• Rename the cucumber package to io.cucumber
• Remove cyclical package dependencies
• Remove split packages
• Make clear the internal structure of the code.
• Do not break the public api (That can wait for the next Gherkin)

Details

Everything outside of cucumber.api has been moved to io.cucumber. And each module uses io.cucumber.<module-name> as its root package. If a module name starts with cucumber-, this part is omitted. This prevents a split package from occurring.

By making as many classes package private as possible it became possible to hide significant parts of cucumbers implementation details. This will make it easier to apply semantic versioning in the future.

By making classes final the use of Mockito was forced to the edges of the package. Ensuring that the exercises each package from end to end.

Before:

After

Types of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).

[coveralls]

Coverage increased (+1.0%) to 86.55% when pulling c2debf3 on introduce-new-package-structure into c75603d on master.

[lock]

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.