These are chat archives for yasp-dota/yasp

22nd
Apr 2015
EgejVencelj
@EgejVencelj
Apr 22 2015 12:06
Nice! I'll try to fork this whole thing and learn/do some work :) Little background in web field, but got some general programming background. Are there any requests on some feedback pages?
Daniel Houston
@DanielHouston
Apr 22 2015 13:56
So it seems that changing the package names in the parser from yasp to co.yasp has, in some way, caused the tests to fail. More explicitly the one-jar process throws a ClassNotFound exception looking for co.yasp.Main.
I hope I've not got something configured somewhere?
Howard Chung
@howardchung
Apr 22 2015 14:16
@EgejVencelj we are tracking issues on GitHub, let us know if there's something you'd like to work on: https://github.com/yasp-dota/yasp/issues
Howard Chung
@howardchung
Apr 22 2015 14:30
@DanielHouston I'm not sure what that might be. Have you tried a clean rebuild? Is this a compile or runtime error?
I'd suspect you missed a spot in changing the package name, but I can't be sure
Daniel Houston
@DanielHouston
Apr 22 2015 14:34
Yep I've rebuilt. This happens at test runtime I think. (I don't have the failure in front of me atm.) I've actually got the retriever running with the changes to the parser in the code (So it must have made it's way through the build ok.
EgejVencelj
@EgejVencelj
Apr 22 2015 14:52
@howardc93 Cool! I will first have to get myself a look around :)
Howard Chung
@howardchung
Apr 22 2015 15:52
The parser is completely independent of the retriever. So it's possible for the parser to be broken with retriever working properly
Daniel Houston
@DanielHouston
Apr 22 2015 16:03
Of course - But I'd expect it wouldn't build at all to be able to run the retriever if there was a compile time problem.
Howard Chung
@howardchung
Apr 22 2015 17:19
The retriever doesnt need to build, since it's all javascript.