Description of problem: The c.a.packaging.Checklist class contains a number of checks for items such as JAAS / JCE jars, DB driver, etc. Unfortunately all these checks are implemented as private methods of the class and there is no mechanism for providing news checks which doesn't involve hacking the source. Checklist should be fixed such that each 'check' is encapsulated in its own 'plugin' class. A config mechanism would be used to register validation plugins with the tool, enabling new tests to be trivially added as problems come to light. This would also enable projects to plugin customer/project specific checks without forking the code. Without this capability, the Checklist tool is severely limited in its usefullness. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
bug 98494 contains a growing list of items to check
-> bstein for clarification as per email
bstein says: A check needs to have some metadata associated with it: * Package with which it is associated (ie, forum / atoz / etc) * Point at which to run. (ie, pre-DB load, pre-Java load, pre-Hostinit, pre-Startup).
This should be implemented now as of change 38433. See the javadoc for com.arsdigita.packaging.Check for details on the use of this feature.
One more thing I forgot, even though the javadoc says that the checks of type "startup" are done on server startup this currently doesn't happen, they are only actually run by the ccm status command. If we want them to be run on server start we should generate a ticket for dennis to make ccm start do the equivalent of running ccm status.