When creating a custom ClassPath and/or using Maven to define a ClassPath for a Java-based application, developers will often forget/leave out the Bedrock dependencies, required for launching and running the said Java applications.
For example, developers should always include the class path of the Bedrock JavaApplicationRunner, otherwise Bedrock will fail to launch the application.
While adding this automatically is a good default, we should provide an option to explicitly enable/disable this ClassPath / dependencies change.
When creating a custom ClassPath and/or using Maven to define a ClassPath for a Java-based application, developers will often forget/leave out the Bedrock dependencies, required for launching and running the said Java applications.
For example, developers should always include the class path of the Bedrock JavaApplicationRunner, otherwise Bedrock will fail to launch the application.
While adding this automatically is a good default, we should provide an option to explicitly enable/disable this ClassPath / dependencies change.