Closed IvoryC closed 4 years ago
On the same system that generated that log file (in description), the biolockj-api listModules
command does not work. So this is actually a real bug, because the issue is that the Reflections functionality is not working on that system, and thus the api function does not work as advertised.
This has been fixed as of PR #49 Af potential reflection fix
It works on my mac. I think its working on the cluster (linux system). At least on my machine it works in docker.
But on Dr. Fodors machine (Ubuntu for Winodows) it looks like the feature is broken. We ran the test case that specifies RdpClassifier without the full class path. The error we get is correct. It correctly states that RdpClassifier is not a valid module; but the feature of finding the module with that name, or suggesting classes with that name... that added feature is not working. Right now our documentation shows that you have to give the full class path, so the ability to use just the class name being system-specific is kind of ok.
The error it shows at the command line is:
The sort of looks like the Reflections part (where it finds all modules in scope) is not working, but that must be working on Dr. Fodors system because I think the biolockj-api does work, and it depends on the same Reflections functions.
Here is an excerpt from the log: