Jar distribution does not appear to read properties file
@fchimien noticed that the properties file appears not to be read:
- when trying extractor=SNER, the code complains:
2020-09-01 17:58:26 INFO Experiment:340 - Experiment could not complete.
2020-09-01 17:58:26 ERROR Experiment:341 - Cause: SNER is not a valid extractor type.
com.beust.jcommander.ParameterException: SNER is not a valid extractor type.
-
when trying extractor=FLAIR, the code complains about the exact same thing (SNER)!
-
when trying extractor=ABC, the code still complains about "SNER not being a valid extractor type".
I reproduced these bugs myself: I made a fresh copy of connectionlens and tried with the attach properties (I tried with SNER, FLAIR, NONE, and ABC...)
I suspect it ends by saying "SNER not valid" because SNER happens to have the code 0 (the first extractor we got) and when the extractor number is "non filled" it "happens" to remain at 0.
I have the properties file under core/settings as it is in the deposit. The Readme on the main page of the project says at the top the file is under core and under the Docker section, that the file is under core/settings. I also tried with the file under core/settings but it wasn't any better.
@tmerabti can you please look into this first thing tomorrow? It's a bit urgent. Thanks!