lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From synhershko <...@git.apache.org>
Subject [GitHub] lucenenet issue #179: Analysis work - Standard and Core namespaces (mostly)
Date Tue, 23 Aug 2016 23:15:49 GMT
Github user synhershko commented on the issue:

    https://github.com/apache/lucenenet/pull/179
  
    Awesome work, thanks Shad!
    
    Sorry for not responding earlier. Upgrading hunspell sounds legit (tho more work), but
it seems you already figured out a solution. Putting all test files in https://github.com/apache/lucenenet/tree/master/test-files
sounds legit - unless Java Lucene are not doing this and disable those tests themselves. Worth
chatting with @wwb here or on the mailing list to see how we can still enable those tests
on the build server.
    
    I'm going to merge this one now into the analysis-work branch, and let's continue the
discussion on the failing tests in the mailing list? Ultimately I'd like to make all tests
green before merging to master, but I'm not sure what is the scope of the failures?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message