Thanks Alex, looks like that was probably a fat-fingered auto-import on my part.
I like your idea, and I don't know the best way to to start either, but maybe one suggestion is to start with one or two focused things to clean up, and then ask for volunteers to take on specific modules? Then people can contribute an hour here and there to do cleanup on their task/module and try to fix that thing in a 1-2-month long sprint. I am happy to contribute to cleanup, I am responsible for my fair share of unclean code, but since I don't have strong software engineering chops it would be good to have people with that background propose the tasks and describe exactly what needs to be done. My idea of cleaning is just to delete commented out sections of evaluation code. Tim ________________________________________ From: Alexandru Zbarcea <[email protected]> Sent: Friday, November 17, 2017 4:46 PM To: Apache cTAKES Dev Subject: unknown dependencies [EXTERNAL] Hi, I notice that a miss-dependency has slipped in the code: jdk.internal.org.objectweb.asm.commons.AnalyzerAdapter; Now, that the Jenkins builds is successful, I think it is easier to clean-up the code. I would like to be a common effort. I don't know the best way to approach this. Looking forward to your advice, Alex
