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
{{ message }}
Repository navigation
[go-migration] Needed dependencies/jars not added to the classpath properly #1179
The final classpath used after staging on application startup is not assembled properly or not added with the needed dependencies on multiple occasions:
deps/index/env/CLASSPATH is overwritten and further unused on actual startup
Multiple frameworks currently in the go-based buildpack overwrite instead of append to the deps/<index>/env/CLASSPATH which is to be used for adding to the classpath on startup. For example having both client-certificate-mapper and java_cfenv frameworks participate on staging, they will both write to CLASSPATHhere and here and only whoever framework writes last entry will be left in the final CLASSPATH.
Moreover seems deps/<index>/env/CLASSPATH is currently not taken into concern at all in Release phase where the actual startup command is being built.
Gathered dependencies during staging phases are never actually used on the corresponding container Release to enrich the application classpath. For example tomcat container adds a custom setenv.sh script where tomcat-logging-support-X.Y.Z.RELEASE.jar is added to the classpath but if any other dependency framework is at place, the corresponding dependency is never considered. For example if one of the following is detected:
postgresql jdbc driver
maria db jdbc driver
spring auto reconfiguration (spring related)
java cf env (spring related)
client certificate mapper
these are not considered on application startup classpath
-Xbootclasspath/a:<dependency> is used on a couple of occasions instead of adding with -classpath. This makes the corresponding dependencies to be appended to the JVM’s boot class loader without some obvious reason for this. Seems this is some AI generation peculiarity for these components. Affected stuff:
changed the title [-][go-migration] deps/<index>/env/CLASSPATH is overwritten and further unused on actual startup[/-][+][go-migration] Needed dependencies/jars not added to the classpath properly[/+]on Mar 8, 2026
Activity
[-][go-migration] deps/<index>/env/CLASSPATH is overwritten and further unused on actual startup[/-][+][go-migration] Needed dependencies/jars not added to the classpath properly[/+]