You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[go-migration] Add dependencies to application classpath after staging (#1208)
Framework JAR dependencies (e.g. MariaDB JDBC, PostgreSQL JDBC,
Spring Auto-reconfiguration, Java CF Env, Client Certificate Mapper)
were written to deps/index/env/CLASSPATH during staging but that
file is never sourced at runtime, so the dependencies were silently
dropped from the application classpath.
- Replace WriteEnvFile("CLASSPATH", ...) with WriteProfileD() scripts
in all framework finalizers so CLASSPATH is assembled correctly at
runtime when profile.d scripts are sourced
- Extract container_security_provider JAR path into a
CONTAINER_SECURITY_PROVIDER env var (set via profile.d) and thread
it through tomcat (setenv.sh CLASSPATH) and spring-boot (via
-cp / -Dloader.path flags) instead of using -Xbootclasspath/a
- Add a zzz_classpath_symlinks.sh profile.d script for tomcat
(WEB-INF/lib) and spring-boot (BOOT-INF/lib) containers that
symlinks every entry on CLASSPATH into the container's lib
directory so deps are subject to application class-loading
- Allow symlinked resources in Tomcat context.xml
(allowLinking='true')
- Remove redundant context struct construction in finalizeFrameworks;
reuse the ctx already built in Run()
0 commit comments