[jira] [Commented] (LUCENE-1344) Make the Lucene jar an OSGi bundle
[ https://issues.apache.org/jira/browse/LUCENE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13059196#comment-13059196 ] Philipp Nanz commented on LUCENE-1344: -- Can someone explain this to me: This issue is marked as resolved in 3.3, it's even listed in the changelog for 3.3, yet the lucene-core.jar file is clearly not OSGI-enabled... What's up with that?! Make the Lucene jar an OSGi bundle -- Key: LUCENE-1344 URL: https://issues.apache.org/jira/browse/LUCENE-1344 Project: Lucene - Java Issue Type: Improvement Components: general/build Reporter: Nicolas Lalevée Assignee: Ryan McKinley Priority: Minor Fix For: 3.3, 4.0 Attachments: LUCENE-1344-3.0-branch.patch, LUCENE-1344-maven.patch, LUCENE-1344-r679133.patch, LUCENE-1344-r690675.patch, LUCENE-1344-r690691.patch, LUCENE-1344-r696747.patch, LUCENE-1344.patch, LUCENE-1344.patch, LUCENE-1344.patch, LUCENE-1344.patch, LUCENE-1344.patch, LUCENE-1344.patch, MANIFEST.MF.diff, lucene_trunk.patch In order to use Lucene in an OSGi environment, some additional headers are needed in the manifest of the jar. As Lucene has no dependency, it is pretty straight forward and it ill be easy to maintain I think. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] Created: (LUCENE-2202) PhraseQuery will not find hits containing stop words when StandardAnalyzer with 2.9 or 3.0 semantics is used
PhraseQuery will not find hits containing stop words when StandardAnalyzer with 2.9 or 3.0 semantics is used Key: LUCENE-2202 URL: https://issues.apache.org/jira/browse/LUCENE-2202 Project: Lucene - Java Issue Type: Bug Components: Analysis Affects Versions: 3.0 Environment: JRE6 Reporter: Philipp Nanz When you add a document with an analyzed field containing a stopword to the index using standardanalyzer, the behaviour will be inconsistent depending on which version semantics where used with StandardAnalyzer. Using 2.4 semantics the document can subsequently be found using PhraseQuery. Using the very same test with 2.9 or 3.0 semantics will fail. -- 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: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
[jira] Updated: (LUCENE-2202) PhraseQuery will not find hits containing stop words when StandardAnalyzer with 2.9 or 3.0 semantics is used
[ https://issues.apache.org/jira/browse/LUCENE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Nanz updated LUCENE-2202: - Attachment: TestCase.java Added Junit4 testcase that exhibits the problem. PhraseQuery will not find hits containing stop words when StandardAnalyzer with 2.9 or 3.0 semantics is used Key: LUCENE-2202 URL: https://issues.apache.org/jira/browse/LUCENE-2202 Project: Lucene - Java Issue Type: Bug Components: Analysis Affects Versions: 3.0 Environment: JRE6 Reporter: Philipp Nanz Attachments: TestCase.java When you add a document with an analyzed field containing a stopword to the index using standardanalyzer, the behaviour will be inconsistent depending on which version semantics where used with StandardAnalyzer. Using 2.4 semantics the document can subsequently be found using PhraseQuery. Using the very same test with 2.9 or 3.0 semantics will fail. -- 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: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
[jira] Commented: (LUCENE-2202) PhraseQuery will not find hits containing stop words when StandardAnalyzer with 2.9 or 3.0 semantics is used
[ https://issues.apache.org/jira/browse/LUCENE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798541#action_12798541 ] Philipp Nanz commented on LUCENE-2202: -- Hello Robert, many thanks for your help and sorry for posting this bogus! PhraseQuery will not find hits containing stop words when StandardAnalyzer with 2.9 or 3.0 semantics is used Key: LUCENE-2202 URL: https://issues.apache.org/jira/browse/LUCENE-2202 Project: Lucene - Java Issue Type: Bug Components: Analysis Affects Versions: 3.0 Environment: JRE6 Reporter: Philipp Nanz Attachments: TestCase.java When you add a document with an analyzed field containing a stopword to the index using standardanalyzer, the behaviour will be inconsistent depending on which version semantics where used with StandardAnalyzer. Using 2.4 semantics the document can subsequently be found using PhraseQuery. Using the very same test with 2.9 or 3.0 semantics will fail. -- 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: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
