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 CLASSPATH here 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.