To avoid super massive classes, I think it would be could to change the current class to be the configuration class.
Then have a separate class handle runtime, specifically, performance/resource statistics, run time modifcations (log level, datasource pool sizes), deployment/undeployment, restarts, etc.
Changed the JBCliPy class to Configuration, which is more descriptive I think...Will work nicely with the RunTime class too I think. See commit detailed above
To avoid super massive classes, I think it would be could to change the current class to be the configuration class.
Then have a separate class handle runtime, specifically, performance/resource statistics, run time modifcations (log level, datasource pool sizes), deployment/undeployment, restarts, etc.