@ApiModelProperty required=false is overriden by @NotNull annotation

Please consider this example:

@ApiModelProperty(required = false, value = "Required only for Ipsum group")
@NotNull(groups = Ipsum.class)
private int lorem;

In this case we have @NotNull annotation, but with specified validation group. Because of that in swagger this property shouldn’t be marked as required so we add required=false in @ApiModelProperty. Unfortunately @NotNull annotation seems to have priority over Swagger own @ApiModelProperty and lorem is still marked as required.

[m-radzikowski]

Well, it’s weird that external (@NotNull) annotation has priority over library’s own annotation (@ApiModelProperty) when it comes to displaying library-specific stuff…

[kimjuny]

This is a reasonable request, because we want the api model itself to be reusable when dealing with different type of input situation. I think a feasible solution could be something like notNullGroups inside ApiModelProperty, but again, that would be waste since the NotNull validator has already declared the group.