The following code is 100% valid and prints:

Init
Validate: true
Execute: 1
Update
Validate: true
Execute: 2
Update
Validate: false
Exit
0
1
2
3
4
5
6
7
8
9

import static java.lang.System.out;

public class ForLoop {
    public static void main(String args[]) {
        for (int i = init(); isTrue(i); i++, out.println("Update")) {
            out.println("Execute: " + i);
        }
        out.println("Exit");

        int i = 0;
        for( ; ; ) {
            if (i < 10) {
                out.println(i);
            }
            else {
                break;
            }
            i++;
        }
    }

    private static boolean isTrue(int i) {
        boolean val = i < 3;
        out.println("Validate: " + val);
        return val;
    }

    private static int init() {
        out.println("Init");
        return 1;
    }
}

You can ignore using criterias to do so:

<sonar.issue.ignore.multicriteria>serializable</sonar.issue.ignore.multicriteria>
<sonar.issue.ignore.multicriteria.serializable.ruleKey>squid:S1948</sonar.issue.ignore.multicriteria.serializable.ruleKey>
<sonar.issue.ignore.multicriteria.serializable.resourceKey>**/*.java</sonar.issue.ignore.multicriteria.serializable.resourceKey>

Watch out for Unsynchronized Entities

One thing to watch out for when updating entities like this, is that the EntityManager may contain outdated entities after the query has executed. This could be the case if your JPA provider uses a cache (such as Hibernate’s second level cache), or if there are changes that are pending to be flushed. As a result, the state of the entities in the EntityManager may not be accurate. This would be the case if an entity affected by the update query is referenced in the EntityManager. One may wonder why the EntityManager is not just cleared after executing the query to avoid this inconsistency, but the reason for this is that there might be changes that have not yet been flushed, that would then be lost. However, you do get the option of configuring this by setting the clearAutomatically attribute of the @Modifying annotation to true.

My father worked in this project at IBM.

This is freaking awesome.

@Table(uniqueConstraints = [UniqueConstraint(columnNames = ["unique_column"])])

This is great. This is the only way to get a portable JDK.