Fix issue #907 by ensuring the parameters is properly "exploded"

[GregDThomas]

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh
  

  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  For Windows users, please run the script in Git BASH.
• In case you are adding a new generator, run the following additional script :

  ./bin/utils/ensure-up-to-date.sh
  

  Commit all changed files.
• File the PR against the correct branch: master (6.3.0) (minor release - breaking changes with fallbacks), 7.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10)

This PR ensures that an exploded query parameter is properly handled by the java-resttemplate code generator, fixing #907

[wing328]

@GregDThomas thanks for the PR. Can you please PM me via Slack when you've time?

https://join.slack.com/t/openapi-generator/shared_invite/zt-12jxxd7p2-XUeQM~4pzsU9x~eGLQqX2g

[GregDThomas]

Just rebased this - is there anything additional I need to do in order to get this merged. Thank you!

[gcatanese]

@wing328 @GregDThomas Using lombok.SneakyThrows, is this correct?

[GregDThomas]

It was certainly intentional on my behalf. I wouldn’t use it in production code, but IMHO it’s fine in test classes. I also suspect (but can’t check right now) it’s probably used elsewhere in the tests too.

[gcatanese]

Ok, I see, thanks

[gcatanese]

The only way I can get it working is to add the lombok dependency in the POM file. Any idea what goes wrong?

[GregDThomas]

Lombok certainly used to be a dependency, as the PR would never have compiled without it. I can’t readily check until next week, but It’s possible that since raising the PR and getting it merged Lombok was removed. A sort of invisible merge conflict I guess.

[wing328]

Added back lombok to pom.xml via 17c2401

[gcatanese]

Sorted now, thank you both

[GregDThomas]

Thank you, and apology for the mess up.