Hello,
this is not a bug - this is a result of an inproper placement of the JAR and classloading mechanics. You can't but a JAR that has a direct dependency on an Alfresco class on the shared/lib/*.jar path since the shared-classloader does not have access to the webapp-specific classloader of Alfresco to load the dependant class BaseEvaluator. Such a JAR can only be put in the WEB-INF/lib of Alfresco.
Regards
Axel