Do we require the contrib to adhere to the same back compatibility rules as trunk? I don't know that it has been established. Thoughts? Analysis is a pretty tricky one, as compared to the other packages.

On Apr 1, 2008, at 8:32 AM, Karl Wettin (JIRA) wrote:


[ https://issues.apache.org/jira/browse/LUCENE-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584119 #action_12584119 ]

Karl Wettin commented on LUCENE-1142:
-------------------------------------

I propose for this patch to be included in Lucene 3.0.0 (3.0.1?)


Updated Snowball package
------------------------

               Key: LUCENE-1142
               URL: https://issues.apache.org/jira/browse/LUCENE-1142
           Project: Lucene - Java
        Issue Type: Improvement
        Components: Analysis
          Reporter: Karl Wettin
          Priority: Minor
       Attachments: snowball.tartarus.txt


Updated Snowball contrib package
* New org.tartarus.snowball java package with patched SnowballProgram to be abstract to avoid using reflection.
* Introducing Hungarian, Turkish and Romanian stemmers
* Introducing constructor SnowballFilter(SnowballProgram)
It is possible there have been some changes made to the some of there stemmer algorithms between this patch and the current SVN trunk of Lucene, an index might thus not be compatible with new stemmers!
The API is backwards compatibile and the test pass.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--------------------------
Grant Ingersoll

Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to