# Application Exception
# ---------------------
# /- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# five framework-embedded messages (don't change key names)
# - - - - - - - - - -/
errors.login.failure = 登入失敗。
errors.app.illegal.transition = 非法轉換，請重試。
errors.app.db.already.deleted = 可能已被其他程序刪除。請重試。
errors.app.db.already.updated = 可能已被其他程序更新。請重試。
errors.app.db.already.exists = 資料已存在。請重試。

character arising as a result of this License or out of the use or inability 
to use the Work (including but not limited to damages for loss of goodwill, 
work stoppage, computer failure or malfunction, or any and all other 
commercial damages or losses), even if such Contributor has been advised of 
the possibility of such damages. 

# Application Exception
# ---------------------
# /- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# five framework-embedded messages (don't change key names)
# - - - - - - - - - -/
errors.login.failure = Accesso fallito.
errors.app.illegal.transition = Transizione illegale. Riprova.
errors.app.db.already.deleted = Potrebbe essere stato eliminato da un altro processo. Riprova l'operazione.

                // ModelBuildingEx is thrown only on FATAL and ERROR severities, but we still can have WARNs
                // that may lead to unexpected build failure, log them
                if (!modelResult.getProblems().isEmpty()) {
                    List<ModelProblem> problems = modelResult.getProblems();
                    if (logger.isDebugEnabled()) {

    public Property<String> getSomeProperty() {
        return someProperty
    }
}
```

Note that managed classes like these need to be instantiated via ObjectFactory so that runtime decorations are applied. Failure to do this will cause strange usability problems in the Groovy DSL.

### New properties in an existing class

    public static final String LABELS_THUMBNAIL = "{labels.thumbnail}";

    /** The key of the message: Ignore Failure Types */
    public static final String LABELS_ignore_failure_type = "{labels.ignore_failure_type}";

    /** The key of the message: Failure Count Threshold */
    public static final String LABELS_failure_count_threshold = "{labels.failure_count_threshold}";

crawler.ignore.robots.tags=false
# Whether to ignore content exceptions during crawling.
crawler.ignore.content.exception=true
# HTTP status codes considered as failure URLs.
crawler.failure.url.status.codes=404
# Interval (seconds) for system monitor during crawling.
crawler.system.monitor.interval=60
# Whether to ignore idle threads in hot thread monitoring.

# Application Exception
# ---------------------
# /- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# five framework-embedded messages (don't change key names)
# - - - - - - - - - -/
errors.login.failure = लॉगिन विफल रहा।
errors.app.illegal.transition = अवैध परिवर्तन। कृपया पुनः प्रयास करें।
errors.app.db.already.deleted = इसे किसी अन्य प्रक्रिया द्वारा हटाया जा सकता है। कृपया पुनः प्रयास करें।

 *     try (ResponseBody responseBody = response.body()) {
 *     ... // Use the response.
 *     }
 *   }
 *
 *   public void onFailure(Call call, IOException e) {
 *   ... // Handle the failure.
 *   }
 * });
 * ```
 *
 * These examples will not work if you're consuming the response body on another thread. In such
 * cases the consuming thread must call [close] when it has finished reading the response

 * hint, so this technique may fail at the whim of the JDK implementation, for example if a user
 * specified the JVM flag {@code -XX:+DisableExplicitGC}. But in practice, it works very well for
 * ordinary tests.
 *
 * <p>Failure of the expected event to occur within an implementation-defined "reasonable" time
 * period or an interrupt while waiting for the expected event will result in a {@link
 * RuntimeException}.
 *