[ https://issues.apache.org/jira/browse/LUCENE-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346804#comment-16346804 ]
ASF subversion and git services commented on LUCENE-8141: --------------------------------------------------------- Commit 505f7b9d56abed389f20d97a16bc5462603b95a3 in lucene-solr's branch refs/heads/branch_7x from [~kwri...@metacarta.com] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=505f7b9 ] LUCENE-8141: Do a better job of making sure polygon points are not coplanar. Committed on behalf of Ignacio Vera. > Inconsistent org.apache.lucene.codecs.PostingsFormat service definition? > ------------------------------------------------------------------------ > > Key: LUCENE-8141 > URL: https://issues.apache.org/jira/browse/LUCENE-8141 > Project: Lucene - Core > Issue Type: Bug > Components: core/codecs > Affects Versions: 7.2.1 > Reporter: Matthias Gärtner > Priority: Minor > > I have a doubt about a seeming inconsistency w.r.t. to a service definition > in the distribution JAR files: > > "lucene-suggest-7.2.1.jar" contains > "org.apache.lucene.search.suggest.document.*Completion50PostingsFormat*" > under "/META-INF/services/org.apache.lucene.codecs.PostingsFormat" (and BTW > _two copies_ of the license in that file?). > > "lucene-core-7.2.1.jar" contains > "org.apache.lucene.codecs.lucene50.*Lucene50PostingsFormat*" under > "/META-INF/services/org.apache.lucene.codecs.PostingsFormat" > > Apparently, it depends on the classpath order on the client side which > implementation is used. Is it *intentional* that there are two unequal > definitions in the same release? > > Note: I've observed this because of some Jar Hell checker output, not because > there's an actual malfunction that I'm aware of. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org