[ 
https://jira.codehaus.org/browse/MINDEXER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313713#comment-313713
 ] 

Tamás Cservenák commented on MINDEXER-67:
-----------------------------------------

Proposed solution: creation of a "focused" component, that will NOT hold any 
context (simply, DefaultNexusIndexer without the {{indexingContexts}} map. This 
component will be then "wrapped" by modified (and deprecated) NexusIndexer 
component, that delegates all the calls to new component, while performs same 
"registry"-like operations and maintains the {{indexingContexts}}.

This means two things:
* users of (deprecated) NexusIndexer component will not notice anything 
(remains bw compat)
* users of new Indexer component will have full control of: indexing context 
used in index operations.

This also makes us able to start "clean slate" with new component, and perform 
gradual "cleanup" of the API.
                
> Provide means to make MI use own IndexingContext implementations
> ----------------------------------------------------------------
>
>                 Key: MINDEXER-67
>                 URL: https://jira.codehaus.org/browse/MINDEXER-67
>             Project: Maven Indexer
>          Issue Type: Improvement
>    Affects Versions: 4.1.3, 5.0.0
>            Reporter: Tamás Cservenák
>             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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to