Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Platform - User Assistance (UA) » Problem with Help indexing when Compass is involved
Problem with Help indexing when Compass is involved [message #614394] Fri, 30 May 2008 14:50
Eric Rizzo is currently offline Eric RizzoFriend
Messages: 2414
Registered: July 2009
Senior Member
A while back I posted a problem we are seeing when help indexing kicks
in (at the time, I thought it had to do with opening the help sidebar,
but it turns out that was just the manifestation of an indexing problem,
because the sidebar includes the Dynamic Help). Here's the original
thread:
http://dev.eclipse.org/newslists/news.eclipse.platform.ua/ms g00198.html

As I've discovered, the problem is due to Lucene's reliance on System
properties to dictate implementation classes. See these Lucene bugs:
http://issues.apache.org/jira/browse/LUCENE-670
http://issues.apache.org/jira/browse/LUCENE-636

The problem boils down to this:
Because Lucene uses a system property (global to the JVM) to allow
customization of the SegmentReader class, any plugin that specifies a
value for that property runs the risk of breaking Eclipse help indexing.
In our case (probably the only one that is very likely), our plugin
depends on Compass; Compass overrides the SegmentReader with its own
implementation, specified by setting the system, property. However,
because Compass is not visible to the help plugin's classloader, Lucene
blows up with a ClassNotFoundException when it tries to initialize itself.
If Eclipse help invokes Lucene first, this problem is avoided (because
Lucene's dependence on that system property is in a static initializer,
only run once per classloader); but if our plugin triggers Compass to
load first, Lucene blows up.

So, I'm looking for a work-around. I'm trying, in my plugin Activator's
start() method, to somehow force Lucene to initialize. But no luck so far.
Any ideas on how to work around this problem?

Also, it seems that this would be a somewhat common problem - I mean,
any plugin that uses Compass (version < 2.0) is going to run into this.
I'm surprised it has not been reported before.

Eric
Previous Topic:Migrating Eclipse 3.2 Help system to 3.3 - language packs
Next Topic:ScrolledFormText horizontal scrollbar (sorry for the cross-post)
Goto Forum:
  


Current Time: Mon Dec 22 21:36:53 GMT 2014

Powered by FUDForum. Page generated in 0.12698 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software