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
JBP_CONFIG_JAVA_MAIN java_main_class and arguments not supported #1267
changed the title [-]Java Main: JBP_CONFIG_JAVA_MAIN java_main_class and arguments not supported[/-][+]JBP_CONFIG_JAVA_MAIN java_main_class and arguments not supported[/+]on May 11, 2026
Additional fix added in this PR: when java_main_class is set, the registry now short-circuits before the normal container detection order, so it correctly overrides higher-priority containers like Spring Boot.
Previously, a Spring Boot app would be detected as Spring Boot before JavaMainContainer.Detect() was ever called, so JBP_CONFIG_JAVA_MAIN had no effect even with the initial fix.
Also added Ruby parity: when java_main_class is one of the Spring Boot launchers (JarLauncher, PropertiesLauncher, WarLauncher), SERVER_PORT=$PORT is now written to profile.d — matching the Ruby buildpack behaviour.
Activity
[-]Java Main: JBP_CONFIG_JAVA_MAIN java_main_class and arguments not supported[/-][+]JBP_CONFIG_JAVA_MAIN java_main_class and arguments not supported[/+]stokpop commentedon May 11, 2026
Additional fix added in this PR: when
java_main_classis set, the registry now short-circuits before the normal container detection order, so it correctly overrides higher-priority containers like Spring Boot.Previously, a Spring Boot app would be detected as Spring Boot before
JavaMainContainer.Detect()was ever called, soJBP_CONFIG_JAVA_MAINhad no effect even with the initial fix.Also added Ruby parity: when
java_main_classis one of the Spring Boot launchers (JarLauncher,PropertiesLauncher,WarLauncher),SERVER_PORT=$PORTis now written to profile.d — matching the Ruby buildpack behaviour.Example:
Branch:
issue-1267-fix-jbp-config-java-main(stokpop fork)