Java generated API uses default Swagger namespace

[danclarke]

The namespace for the API is the default Swagger namespace from codegen. While this does work, if any other SDKs are also code generated with the default namespace they will all conflict. The namespace should be specific to Weather API rather than generic Swagger.

[ferdnyc]

In the python API repo I submitted weatherapicom/python#5 which renamed the project to weatherapipython (as originally documented) and the package namespace to weatherapi.

I also noted that the Python generator in swagger-codegen-cli (the tool used to output these API packages) can be given a non-default name via the argument -DpackageName=weatherapi, though I'm not sure how that works for Java's namespace hierarchy.

Ah, looks like it'd be the arguments -DgroupId="com.weatherapi" -DartifactId="WeatherApi" to generate a com.weatherapi.WeatherApi package... or, alternately, passing a -c /path/to/config.json containing:

{
  "groupId": "com.weatherapi",
  "artifactId": "WeatherApi"
}

...But that info's mostly for @weatherapicom, if they ever choose to regenerate these APIs. It doesn't help downstream users, who AFAICT don't have access to the data (a swagger.json file?) necessary to run swagger-codegen-cli for the weatherapi service.