constraints.AssertTrue.message = {item} doit être vrai.
constraints.DecimalMax.message = {item} doit être inférieur à {value}.
constraints.DecimalMin.message = {item} doit être supérieur à {value}.
constraints.Digits.message = {item} doit être un nombre. (attendu : <nombre>.<nombre>)
constraints.Future.message = {item} doit être une valeur future.
constraints.Max.message = {item} doit être inférieur ou égal à {value}.

constraints.AssertTrue.message = {item} muss wahr sein.
constraints.DecimalMax.message = {item} muss kleiner als {value} sein.
constraints.DecimalMin.message = {item} muss größer als {value} sein.
constraints.Digits.message = {item} muss eine Zahl sein. (erwartet: <Zahl>.<Zahl>)
constraints.Future.message = {item} muss ein zukünftiger Wert sein.
constraints.Max.message = {item} muss kleiner oder gleich {value} sein.

                    out.print("</b></a>");
                } else {
                    out.print("\"><b>");
                    out.print(name);
                    out.print("</b></a><div align='right'>");
                    out.print(f.length() / 1024 + " KB </div><div>");
                    i = name.lastIndexOf('.') + 1;
                    if (i > 1 && name.length() - i < 6) {

        try {
            validateLocalRepository(request);
        } catch (IOException e) {
            return addExceptionToResult(result, e);
        }

        //
        // We enter the session scope right after the MavenSession creation and before any of the
        // AbstractLifecycleParticipant lookups
        // so that @SessionScoped components can be @Injected into AbstractLifecycleParticipants.
        //

There is a somewhat non-obvious filter present on the page that allows you to control which type of messages are displayed.
The filter is a dropdown box that appears when you click the `Severity ⬇️ ` label in the black header bar to the immediate right of the Gradle version.

If you have a large number of messages of different types, filtering by severity to see only `Error`s can be helpful when processing the report.

constraints.AssertFalse.message = {item} 必須為 false。
constraints.AssertTrue.message = {item} 必須為 true。
constraints.DecimalMax.message = {item} 必須小於 {value}。
constraints.DecimalMin.message = {item} 必須大於 {value}。
constraints.Digits.message = {item} 必須是數字。(預期: <數字>.<數字>)
constraints.Future.message = {item} 必須是未來的日期。
constraints.Max.message = {item} 必須小於或等於 {value}。
constraints.Min.message = {item} 必須大於或等於 {value}。
constraints.NotNull.message = {item} 不能為空。

                            * `security_scopes.scopes` wird `[]` (nichts) für die *Pfadoperation* `read_system_status` enthalten, da diese keine `Security` mit `scopes` deklariert hat, und deren Abhängigkeit `get_current_user` ebenfalls keinerlei `scopes` deklariert.

/// tip | Tipp

                                artifact.setDependencyTrail(node.getDependencyTrail());

                                set.add(node);

                                // This is required right now.
                                result.addArtifact(artifact);
                            }
                        }
                    } catch (OverConstrainedVersionException e) {

/// tip

...Although if the whole application is just **crashing immediately** it probably doesn't make sense to keep restarting it forever. But in those cases, you will probably notice it during development, or at least right after deployment.

So let's focus on the main cases, where it could crash entirely in some particular cases **in the future**, and it still makes sense to restart it.

///

These are issues that we believe are particularly well suited for outside
contributions, often because we probably won't get to them right now. If you
decide to start on an issue, leave a comment so that other people know that
you're working on it. If you want to help out, but not alone, use the issue
comment thread to coordinate.