Java 6 was EOL’ed over 4 years ago. I understand the challenge with such clients, but honestly, can’t tell which older version of the codegen would support it, and even if there is one, it’s probably riddled with other bugs that have since been resolved.
Your best bet is to try and modify the existing templates. From: <swagger-swaggersocket@googlegroups.com> on behalf of Sonia Marginean <sonia.margin...@gmail.com> Reply-To: "swagger-swaggersocket@googlegroups.com" <swagger-swaggersocket@googlegroups.com> Date: Monday, 20 March 2017 at 14:16 To: Swagger <swagger-swaggersocket@googlegroups.com> Subject: Swagger codegen version for Java 6 and Jersey 1.17.1 Hello, We have a Java 8 microservice for which we use swagger codegen to generate client SDKs for different older services to use. We generated a Client SDK for Jersey1, but noticed the default version for Jersey1 is 1.17.1 and Java is 1.8. Unfortunately one of our client services is stuck on Java 1.6 and using Jersey1 1.17.1 and they can't upgrade to anything newer. Is there a version of swagger-codegen that would allow that? started messing around with the pom.mustache files but then ran into issues because of JAX-RS. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggersocket+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggersocket+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
