Issues uncovered building some existing projects

[Jack Park]

What I have to say here is in the spirit of learning from what is 'out there'. It is, by now means, meant to be a criticism of any particular project. I have a goal to co-evolve with others a deep understanding of architectures, potentials, and solutions. I have been attempting to build some of the projects.

AKSW OpenQA: building in Eclipse, found some jars missing, and one unresolvable import:  javax.servlet.annotation.WebServlet That bug was fixed by upgrading the servlet-api jar. So, now, we have OpenQA ready to test.

AKSW QA: building with maven: stale maven repos, issue of two separate builds in one project, each requiring the other.

Machine_Reading (internally, kgraph). Ib uses something from OAQA, but the pom is stale. It seems to need the OAQA Graph DB, but that project appears to have matured; the project cannot be built; it also includes hard-wired locations on a particular hard disk. My guess is that this was a student project, abandoned after putting it at GitHub.

DeepQA: built in Eclipse. Builds with no compilation errors, but Eclipse insists "Target runtime Apache v 7.0 is not defined". From what I can tell, that's because I do not have a Server environment in this Eclipse. So, it builds. At the moment, it's not clear what to do with it; not sure how it boots data, where it stores it, etc. Still a lot to learn.

On the lighter side: YodaQA came up. My experiments with it are documented in a wiki page at the YodaQA repo.

I built a copy of Netention. Had it online running fine. Of course, it's not really a question answering platform, but it is a powerful user interface, capable of supporting such projects.

Up next will be to build Watsonsim, and to attempt to get DeepQa and OpenQA running.

[Sean Gallagher]

I would be astonished if WatsonSim ran correctly the first time. We have been trying to run it on multiple systems on the campus and have resolved a few issues but I look forward to hearing what you find.

- Sean

[Jack Park]

I've been warned ;-)

So what?  For me, building on Windoz, the holdup was originally based on databases, but now that's resolved.

The other issues are ones based on stale pom.xml files and so forth. I can probably conquer some of those by simply grabbing all the dependences together and building in Eclipse.  

But, I'm guessing that stale projects mean they served a purpose, then were followed by something newer/better, or simply abandoned.  For me, the game is to get the code into Eclipse and study it while it is running.

--
You received this message because you are subscribed to the Google Groups "qa-oss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qa-oss+un...@googlegroups.com.
To post to this group, send email to qa-...@googlegroups.com.
Visit this group at http://groups.google.com/group/qa-oss.
To view this discussion on the web visit https://groups.google.com/d/msgid/qa-oss/ffdc668a-ebe1-4de4-a941-620b241804af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.