We're updating the issue view to help you get more done. 

The annotation processor should allow constraint annotations at non-getter methods

Description

Currently the AP creates a compiler error if any non-getter method is annotated with constraint annotations. With the introduction of the method validation feature this check is no longer correct, the AP should allow constraints at any non-static, non-void method.

We might also introduce a processor option that controls, whether constraints at non-getters are allowed or not. That way users who don't work with method validation could keep the current behavior.

Environment

None

Status

Assignee

Unassigned

Reporter

Gunnar Morling

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Priority

Major