Extract refresh models into separate module

[evabishchevich]

This PR introduces one more module with DTOs for Direction Refresh API

[LukasPaczos]

Are there any duplicated auto value classes generated when building the /services module?
See

mapbox-java/services/build.gradle

Lines 25 to 32 in 1a932c1

	// Required because the autovalue picks up and generates duplicate class for walking options from services-directions-models,
	// possibly because they are in the same package as the rest of services-directions.
	// Placing them in the same package has been intentional to avoid breaking changes.
	tasks.withType(Jar) { jarTask ->
	if (!jarTask.name.endsWith("sourcesJar")) {
	jarTask.exclude("**/*WalkingOptions*.class")
	}
	}

[evabishchevich]

Are there any duplicated auto value classes generated when building the /services module?
See

mapbox-java/services/build.gradle

Lines 25 to 32 in 1a932c1

	// Required because the autovalue picks up and generates duplicate class for walking options from services-directions-models,
	// possibly because they are in the same package as the rest of services-directions.
	// Placing them in the same package has been intentional to avoid breaking changes.
	tasks.withType(Jar) { jarTask ->
	if (!jarTask.name.endsWith("sourcesJar")) {
	jarTask.exclude("**/*WalkingOptions*.class")
	}
	}

There is no such problem. Checked in mavenLocal

[Guardiola31337]

I believe we should keep adding the explicit dependency until it's released. Same for services-directions-refresh-models cc @LukasPaczos

[LukasPaczos]

yea, I think that's correct

[evabishchevich]

Do we still want to keep it as explicit dependency?
@LukasPaczos @Guardiola31337

[LukasPaczos]

Bintray repo is available here https://bintray.com/mapbox/mapbox/mapbox-sdk-directions-refresh-models.

[LukasPaczos]

🚢