[
https://jira.codehaus.org/browse/MINDEXER-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308321#comment-308321
]
Tamás Cservenák commented on MINDEXER-57:
-----------------------------------------
This change introduces a _slight_ API change, noticeable if you tamper with
{{IndexingContext}} at low level. For example, Sonatype Nexus integration
required _no source change_ at all (if you don't count one Unit Test that did
tamper with IndexingContext at low level, to bring index into desired state).
For examples of needed code changes, see here:
https://github.com/cstamas/maven-indexer-examples/commit/eb38e442889d072d380c8fb18e5f35a5dd372076
https://github.com/sonatype/nexus/commit/1b2f83c177428469edd53ce1994574db0f3cc986
> Make use of new Lucene 3.5+ API
> -------------------------------
>
> Key: MINDEXER-57
> URL: https://jira.codehaus.org/browse/MINDEXER-57
> Project: Maven Indexer
> Issue Type: Improvement
> Reporter: Tamás Cservenák
> Assignee: Tamás Cservenák
> Fix For: 5.0.0
>
>
> Make use of new Lucene 3.5+ API.
> Lucene introduced some nice new APIs (and they got into core in 3.6). Since
> MI is bumped to Lucene 3.6, it should make use of those. Most of these
> relates to searcher lifespan management, something that was done by very
> involved locking and "bottlewarmer" features of MI, something that should be
> completely removed.
> See:
> http://blog.mikemccandless.com/2011/11/searcherlifetimemanager-prevents-broken.html
> http://blog.mikemccandless.com/2011/11/near-real-time-readers-with-lucenes.html
--
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
