The Eclipse platform is planning to transition from Lucene 2.9 to 3.5 in 
the Kepler release [1]. This will hopefully be released in the M1 
milestone. I am announcing this here because it is a major new Lucene 
version and there are many breaking API changes within Lucene itself. 
Also, two Eclipse platform bundles were exposing and re-exporting Lucene 
APIs (org.eclipse.help.base and org.eclipse.help.ui). We realized this 
problem several years ago and the related APIs on our side were deprecated 
and their future removal was announced on this list over two years ago 
[2]. These deprecated Eclipse platform APIs will be deleted in  Kepler and 
we will no longer re-export or expose Lucene. These changes will insulate 
the platform against future breaking Lucene changes and allow us to adopt 
new Lucene versions more quickly in the future.  This will all be 
documented in the Kepler migration guide but I wanted to give projects a 
heads up here before the changes actually arrive in the release train. 
Feel free to follow up either here or in the bug report with any questions 
or concerns.

John


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=340563
[2] 
http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg04077.html
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to