Published pom.xml' have all dependencies marked "runtime" scope instead of "compile" scope

[pvdissel]

We were made aware of this "issue" by a user who noticed all openapi-java-client dependencies to be marked "runtime" instead of "compile" scope. Thanks making us aware of this.

This is not really an issue, as users of the openapi-java-client will still get all dependencies they need to run the client. It's just a technical "this could be more tidy" thingy, and therefor not an issue.

The cause of this untidyness is the build system version was released with, namely Gradle version 1.x.
This version, and some version later, had the following bug gradle/gradle#1118 which caused all dependencies in the published pom.xml to be marked "runtime" instead of their correct scope.

Doing a new release to tidy this up isn't worth the effort.
But it would be good to take this issue into account for a new feature release, doing some tidying up at the same time.