[Java] inconsistent version 2.1.6 in mavencentral with current code in github

[martinmuellerrohde]

Note: we noticed CodegenModel.java with Map<String, Object> allowableValues is missing in a Swagger-codegen jar downloaded from Maven-central.

There seems to be an inconcistency:

If Maven retrieves version 2.1.6 from maven-central it gets the version with CodegenModel.java where allowableValuesis represented as a List<String>.

If downloading the latest code from github it also creates a version 2.1.6 but this time with CodegenModel.java where allowableValuesis represented as a Map<String, Object>.

In other words:
The releases tagged as 2.1.6 doesn't contain your great additions in CodegenModel.java for enum key/value-pairs.
Even though thoses changes were prior to 2.1.6 they are not included in the release dated from April 6th 2016.

I really would like to use the new enum-features and don't know how to make my build-process stable if it downloads the wrong version.

Swagger-codegen version: 2.1.6

Proof:
Compare content of
http://central.maven.org/maven2/io/swagger/swagger-codegen/2.1.6/swagger-codegen-2.1.6.jar
with your latest code.

Suggestion:
a) change the version in your pom.xml from 2.1.6 to 2.1.7-SNAPSHOT
b) tag the latest code with Map<String, Object> allowableValues to make it available for download via mavencentral

[wing328]

@martinmuellerrohde I've merged #2950 into master to update the version to 2.2.0-SNAPSHOT (which is the next stable version)

[martinmuellerrohde]

Thank you @wing328 !
Currently your README.md still says "2.1.7-SNAPSHOT" even though it is 2.2.0-SNAPSHOT now.

[wing328]

@martinmuellerrohde updated :)

[wing328]

For allowableValues it's a breaking change due to the need to have better enum support. Please refer to #2508 (comment) for more information.

[martinmuellerrohde]

Super !
Now I guess I still need it to be published at maven central, right?

[wing328]

@martinmuellerrohde I do not have right to do that. I think @fehguy and @webron are busy at the CloudFoundry Summit.

Can you do a mvn install to install the 2.2.0-SNAPSHOT version locally for the time being?

[fehguy]

Hi, we are definitely not ready to release 2.2.0, but we can do a patch release of 2.1.7 whenever @wing328 is ready.

[wing328]

@martinmuellerrohde it usually takes 3 to 4 months to release a stable version. I think your request is to upload 2.2.0-SNAPSHOT (not 2.2.0) to maven repo for the time being, right?

[fehguy]

I would suggest that we don't do that though, because 2.2.0 will have some major changes in packaging and it'll break @martinmuellerrohde 's deployment when that happens...

[martinmuellerrohde]

Oh, yes.
You are right.
A patch version 2.1.7 would be a lot nicer.

[heikom71]

Same problem like @martinmuellerrohde in my project - a patch version 2.1.7 would be fantastic...

[wing328]

We'll release 2.2.0 soon.

Closing this issue.