[Core] Formalize glue and feature paths

[mpkorstanje]

Summary

Feature Path

The feature path was poorly defined. It could either be a path or
a path with a classpath: prefix. This ambiguity allowed room
for various inconsistencies and misinterpretations.

1. Pickle URI's were not actually uniform. Depending on operating
   system different path seperators would be used.

2. Pickle URI's did not identify a resource. The classpath:
   prefix would be dropped after loading a feature file. This
   lead to a fairly complex try-catch-try-again-on-the-classpath
   mechanism when loading rerun file.

By properly defining the feature identifier it becomes possible to
parse it in RuntimeOptions and propagate a consistent URI to
other parts of cucumber-jvm. This reduces the need for work
arounds in various places.

Features are identified by a URI. This URI can either be absolute:
scheme:/absolute/path/to.feature, or relative to the
current working directory:scheme:relative/path/to.feature.

In either form, when the scheme is omitted file will be
assumed: path/to.feature.

On systems that use a File.separatorChar other then /
File.separatorChar can be used as a path separator. When
doing so when the scheme must be omitted: path\to.feature.

It is recommended to use / as the path separator.

Fixes: #1547

Glue Path

Likewise the feature path was poorly defined. It could be a resource
name, a classpath URI or a file path. This ambiguity allowed room
for various inconsistencies and misinterpretations.

The glue path can now be written as either a package name: com.example.app
a path com/example/app or uri classpath:com/example/app.

On file system with a path separator other then / com\example\app
is also a valid glue path.

It is recommended to always use the package name form.

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).

Checklist:

• I've added tests for my code.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[coveralls]

Coverage decreased (-0.2%) to 86.029% when pulling fafe09f on refactor-resource-loading into 5d062e7 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.