# specific language governing permissions and limitations
# under the License.

# -----------------------------------------------------------------------------
# Apache Maven Startup Script
#
# Environment Variable Prerequisites
#
#   JAVA_HOME           (Optional) Points to a Java installation.
#   MAVEN_ARGS          (Optional) Arguments passed to Maven before CLI arguments.

constraints.NotBlank.message = {item} は未入力です。
constraints.NotEmpty.message = {item} は未入力です。
constraints.ParametersScriptAssert.message = スクリプト式「{script}」がtrueではありません。
constraints.Range.message = {item} は {min} から {max} の範囲にある必要があります。
constraints.SafeHtml.message = {item} は危険な HTML コンテンツを含んでいます。
constraints.ScriptAssert.message = スクリプト式「{script}」がtrueではありません。
constraints.URL.message = {item} は有効なURLではありません。
constraints.Required.message = {item} が必要です。

# under the License.
# ----------------------------------------------------------------------------

# ----------------------------------------------------------------------------
# Apache Maven Wrapper startup batch script, version 3.3.2
#
# Required ENV vars:
# ------------------
#   JAVA_HOME - location of a JDK home dir
#
# Optional ENV vars
# -----------------
#   MAVEN_OPTS - parameters passed to the Java VM when running Maven

owExternal) }} Note: Since NetworkPolicy is enabled, only pods with label {{ template "minio.fullname" . }}-client=true" will be able to connect to this minio cluster. {{- end }} minio/templates/_helper_create_bucket.txt #!/bin/sh set -e ; # Have script exit in the event of a failed command. {{- if .Values.configPathmc }} MC_CONFIG_DIR="{{ .Values.configPathmc }}" MC="/usr/bin/mc --insecure --config-dir ${MC_CONFIG_DIR}" {{- else }} MC="/usr/bin/mc --insecure" {{- end }} # connectToMinio # Use a...

owExternal) }} Note: Since NetworkPolicy is enabled, only pods with label {{ template "minio.fullname" . }}-client=true" will be able to connect to this minio cluster. {{- end }} minio/templates/_helper_create_bucket.txt #!/bin/sh set -e ; # Have script exit in the event of a failed command. {{- if .Values.configPathmc }} MC_CONFIG_DIR="{{ .Values.configPathmc }}" MC="/usr/bin/mc --insecure --config-dir ${MC_CONFIG_DIR}" {{- else }} MC="/usr/bin/mc --insecure" {{- end }} # connectToMinio # Use a...

owExternal) }} Note: Since NetworkPolicy is enabled, only pods with label {{ template "minio.fullname" . }}-client=true" will be able to connect to this minio cluster. {{- end }} minio/templates/_helper_create_bucket.txt #!/bin/sh set -e ; # Have script exit in the event of a failed command. {{- if .Values.configPathmc }} MC_CONFIG_DIR="{{ .Values.configPathmc }}" MC="/usr/bin/mc --insecure --config-dir ${MC_CONFIG_DIR}" {{- else }} MC="/usr/bin/mc --insecure" {{- end }} # connectToMinio # Use a...

owExternal) }} Note: Since NetworkPolicy is enabled, only pods with label {{ template "minio.fullname" . }}-client=true" will be able to connect to this minio cluster. {{- end }} minio/templates/_helper_create_bucket.txt #!/bin/sh set -e ; # Have script exit in the event of a failed command. {{- if .Values.configPathmc }} MC_CONFIG_DIR="{{ .Values.configPathmc }}" MC="/usr/bin/mc --insecure --config-dir ${MC_CONFIG_DIR}" {{- else }} MC="/usr/bin/mc --insecure" {{- end }} # connectToMinio # Use a...

Here are some possible ideas:

* An "Init Container" in Kubernetes that runs before your app container
* A bash script that runs the previous steps and then starts your application
    * You would still need a way to start/restart *that* bash script, detect errors, etc.

/// tip

Run the regeneration command:

```bash
# Option 1: Using Maven from project root
mvn dbflute:freegen

# Option 2: Using DBFlute manage script
cd dbflute_fess
./manage.sh    # On Linux/Mac
manage.bat     # On Windows
# Select option 23 (generate)
```

This will regenerate:
- `src/main/java/org/codelibs/fess/mylasta/action/FessLabels.java`

Aquí hay algunas ideas posibles:

* Un "Contenedor de Inicio" en Kubernetes que se ejecuta antes de tu contenedor de aplicación
* Un script de bash que ejecuta los pasos previos y luego inicia tu aplicación
    * Aún necesitarías una forma de iniciar/reiniciar *ese* script de bash, detectar errores, etc.

/// tip | Consejo