Pre-startup initialization listener. Fires on ApplicationPreparedEvent — after Spring context is initialized but before the embedded Tomcat starts accepting connections. 89 lines.

• Base directory creation: ensures logs/, temp/, fonts/, attachments/ directories exist under the configured base directory
• Version banner: reads /META-INF/projectforge-version.properties from the classpath, logs the version number, build timestamp, and Git revision in a formatted banner
• Font directory: writes bundled font files to fonts/ for MerlinFontService
• JVM info: logs JVM name, version, memory settings (heap + non-heap), PID, and classpath version using ManagementFactory.getRuntimeMXBean()
• Plugin activation: triggers ProjectForgeApp plugin initialization — discovers all plugins via ServiceLoader and calls their initialize() methods
• Cache warming: calls UserGroupCache warm-up to pre-load user-group mappings before first request

The startup banner is printed using EmphasizedLogSupport with ASCII-art borders — visible in the application log immediately after ApplicationPreparedEvent fires.

Pre-startup initialization listener. Fires on ApplicationPreparedEvent — after Spring context is initialized but before the embedded Tomcat starts accepting connections. 89 lines.

• Base directory creation: ensures logs/, temp/, fonts/, attachments/ directories exist under the configured base directory
• Version banner: reads /META-INF/projectforge-version.properties from the classpath, logs the version number, build timestamp, and Git revision in a formatted banner
• Font directory: writes bundled font files to fonts/ for MerlinFontService
• JVM info: logs JVM name, version, memory settings (heap + non-heap), PID, and classpath version using ManagementFactory.getRuntimeMXBean()
• Plugin activation: triggers ProjectForgeApp plugin initialization — discovers all plugins via ServiceLoader and calls their initialize() methods
• Cache warming: calls UserGroupCache warm-up to pre-load user-group mappings before first request

The startup banner is printed using EmphasizedLogSupport with ASCII-art borders — visible in the application log immediately after ApplicationPreparedEvent fires.