[ben51degrees]

The rerun of the Publish dry run passed every Maven test on every platform and then failed the Selenium contract tests on the six x64 and macOS jobs: all nine cases timed out with the page loaded but the core script never defined.

Cause

The earlier change that named the Device Detection web examples' webapp folder in full fixed the test, which resolves the folder by searching, but the examples' own main method hands that folder to Jetty as a path relative to the working directory. The contract run starts the jar from inside examples/device-detection, so Jetty got examples/device-detection/examples/device-detection/... and served an empty application. The Jetty log line in the job shows exactly that doubled path.

Changes

• Both Device Detection web examples resolve the folder by searching in main as well, so they run from the repository root or from inside their tree.
• The example configurations' default data file paths pointed at the data folders where the separate repositories kept them. They now point at the folders inside the cxx submodule, so an example started from the repository root finds the free data file. The tests were unaffected because they pass the data file in.

What was checked

• The on-premise web example, built against the reactor and started from the repository root, answers 200, its page carries the apple-detection element and the core script tag, and /51Degrees.core.js serves 51 KB that defines fod. Jetty logs the right folder.
• The cloud example needs a resource key, so its check is the rerun of the dry run's Test jobs after this merges.