[Java*] Merge beanValidation/beanValidationParams.mustache

[jfiala]

Description

From #4615: Implement decision of merging beanValidation/beanValidationParams.mustache at the cost of losing the newlines in beanValidation.mustache but with the plus of having to maintain only a single file for all the beanvalidation annotations.

Languages to be updated:

• jaxrs-cxf-cdi
• jaxrs-spec - see PR [Jaxrs-spec] Merge beanValidation/beanValidationParams.mustache #4731
• jaxrs (Jersey) - see PR [Jaxrs-Jersey] Merge beanValidation/beanValidationParams.mustache #4732
• jaxrs-cxf- see PR [Jaxrs-cxf] Merge beanValidation/beanValidationParams.mustache #4733
• jaxrs-resteasy - see PR [Jaxrs-resteasy] Merge beanValidation/beanValidationParams.mustache #4734
• java - see PR [Java] Merge beanValidation/beanValidationParams.mustache #4735
• spring - see PR [SpringBoot] Merge beanValidation/beanValidationParams.mustache #4736

This issue covers also #4711, if beanValidationPathParams/QueryParams are also split during the update, otherwise this has to be done separately.

Swagger-codegen version

2.2.2-SNAPSHOT

Related issues

PR #4615 - there the decision was concluded.

[jfiala]

Implemented merge for jaxrs-cxf-cdi, see PR #4723

[jfiala]

@nickcmaynard

Overview of existing beanvalidation annotations from swagger-with-fake....yaml:

Parameters:

• @NotNull: PetApi.findPetsByStatus(@NotNull ..List status)
• @Min/@max: StoreApi.getOrderById(@min(1) @max(5) ..Long orderId)
• @DecimalMin / @DecimalMax: no sample yet
• @pattern: no sample yet
• @SiZe: no sample yet

Model:

• @NotNull: Pet.getName(), Pet.getPhotoUrls (List)
• @Min/@max: FormatTest.getInt32() @min(20) @max(200)
• @DecimalMin / @DecimalMax: FormatTest.getNumber @DecimalMin("32.1") @DecimalMax("543.2")
• @pattern: FormatTest: getString() @pattern(regexp="/[a-z]/i")
• @SiZe: FormatTest.getPassword() @SiZe(min=10,max=64)

Additionally we can cross out Min/Max and Size(min=/max).
So we could add some more variations to the FormatTest of the swagger-with-fake....yaml, is that what you mean?

Is there any sample of how to assert the generated Parameters/Model annotations with a Junit-test or do we need to set this up (pls see also #4721, I'd prefer to add a Java-based Generator Util class and then a test based on the sample results?
So I'd like first make sure that the samples are always up to date and then do assertions on the various snippets to make sure they stay the same over time.