Add command line interface

[kmadsen]

Resolves https://github.com/mapbox/navigation-sdks/issues/542

Usage

1. build

➜  mapbox-java git:(km-services-cli) ./gradlew shadowJar
or
➜  mapbox-java git:(km-services-cli) make build-cli

2. commands

➜  mapbox-java git:(km-services-cli) java -jar services-cli/build/libs/services-cli-all.jar
Missing required option: f
usage: java -jar services-cli/build/libs/mapboxjava-cli.jar
 -f,--file <arg>   Path to a json file or directory
 -h,--help         Show command line interface usage

3. validate json

➜  mapbox-java git:(km-services-cli) java -jar services-cli/build/libs/services-cli-all.jar -f services-directions/src/test/resources/directions_v5_waypoint_names.json
[{"filename":"directions_v5_waypoint_names.json","success":true,"converts_back":false}]

Alternatives

The original ticket asks to test json on any previous build of mapbox-java, which is a little complicated with gradle - so here was an alternative to make the CLI in NodeJs #1189 - This approach was closed because we would rather build it in kotlin.

Next steps

Distributing
We will want to add this jar to our mapbox-java releases as an asset. Notice how classyshark does this too. This task is to make it so directions api can use them in their CI process.

Features
Currently you can make directions api calls with make commands using curl. This project will allow us to move those commands to use the actual mapbox-java implementation (it's not implemented yet, but this project is set up to hopefully make it easy to do so)

Feel free to add your ideas! This is also written in kotlin, so it will be easier to start building our mapbox-java modules in kotlin.

[kmadsen]

cc: @zugaldia @Guardiola31337 @langsmith

[zugaldia]

This is great @kmadsen - I just gave it a try, no issues. A few random suggestions, in no particular order, some of them could be tracked as tailwork:

1. In addition to validating a JSON, it'd be good if we could set an arbitrary endpoint and execute an actual request like you mention in OP. That way, we could validate, for example, staging endpoints.
2. There's a handy Gradle plugin called shadow that creates "fat jars". It combines a project's dependency classes and resources into a single output jar. This makes the jar heavier, but self-contained.
3. Building on the item above, I'd document the process to attach the resulting jar with every release.

[kmadsen]

2. use shadowJar

Yea thanks for the reminder! removes the TODO because they already solved the problems I was dealing with. it's all updated

1. That way, we could validate, for example, staging endpoints

Yep agree but as tailwork 👍 ; was planning on making that another change so it can receive separate code review

3. I'd document the process to attach the resulting jar with every release.

Tailwork agree 👍 ; Would like to dig in to see if we can make it more automated than documented

[Guardiola31337]

Great work @kmadsen

Left a minor comment (not blocking the PR).

Another follow up would be creating a Gradle plugin that runs the MapboxJavaCli program.

Also don't forget to cut tickets with the tailwork listed in #1198 (comment)

[Guardiola31337]

We should move these to gradle/dependencies.gradle #1198 (comment)