You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Matthias Gärtner (JIRA)" <ji...@apache.org> on 2018/01/30 10:43:00 UTC
[jira] [Created] (LUCENE-8141) Inconsistent
org.apache.lucene.codecs.PostingsFormat service definition?
Matthias Gärtner created LUCENE-8141:
----------------------------------------
Summary: 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
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org