Semantic Matching difference found between console run and maven run when matching same lists

[gpapat26]

When running from command console match between 2 lists a semantic match is found between neighbourhood and places with relation: neighbourhood > places. I also receive as result all the children of places as "owned" be neighboorhod i.e :

neighbourhood > beach
neighbourhood > bridge
neighbourhood > campground
neighbourhood > castle
neighbourhood > village

And also receive these results that belong to different node , nevertheless since there is a connection between neighbourhood and places its ok.

neighbourhood > burrito place
neighbourhood > pizza place neighbourhood > salad place neighbourhood > sandwich place
neighbourhood > snack place neighbourhood > soup place
neighbourhood > taco place

This does not happen when using the maven build .The "neighbourhood" is not matched with "places" and not matched with none of places children . I only receive this as result:

neighbourhood > burrito place
neighbourhood > pizza place neighbourhood > salad place neighbourhood > sandwich place
neighbourhood > snack place neighbourhood > soup place
neighbourhood > taco place

The same happends when matching the word "locality" with "places" the maven build will not act like the console. Same for "country" and "places" .

[moazreyad]

I could not regenerate the issue.

When I put "neighbourhood" in c.txt and "places" in w.txt and run the unit test of the Maven version, the result is neighbourhood > places.

Please provide the 2 lists that you used as input and the steps that you did in the case of Maven version and the case of the other version.

[moazreyad]

I am closing the issue because it can not be reproduced . Please reopen it again if it still happens and provide more details on how to reproduce the error.