[
https://issues.apache.org/jira/browse/MINDEXER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965223#comment-17965223
]
Olivier Lamy commented on MINDEXER-67:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-indexer#515|https://github.com/apache/maven-indexer/issues/515].
> Provide means to make MI use custom IndexingContext implementations
> -------------------------------------------------------------------
>
> Key: MINDEXER-67
> URL: https://issues.apache.org/jira/browse/MINDEXER-67
> Project: Maven Indexer (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 4.1.3, 5.0.0
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 5.1.0
>
>
> Current "main" component of MI (NexusIndexer) serves as main entry for
> indexing operations, but _also serves as context registry_. The latter is
> used in cases like "untargeted search", and happens as "side effect" of
> Indexing Context creations (when you create a context, it will be always
> added to contexts map).
> With latest changes, it becomes obvious to have the two functionalities
> (context/indexing/search manipulation and "context registry") have separated.
> It prevents use of "own" context implementations, but also might interfere
> with searches when a "temp" context is needed and created over Indexer API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
