Geek Answers Handbook

Eclipse: How to ensure that the jar in the plugin takes precedence over other versions elsewhere?

I am developing an eclipse plugin that contains a specific version of Lucene. I need to create a search index and deploy it so that it can be read by another application that uses the same version of Lucene.

I recently upgraded eclipse to 3.4, and the search index is no longer readable by the second application. I see that eclipse 3.4 contains a newer version of Lucene, and I assume that this version is used when creating the index.

How can I pinpoint which version of Lucene is used during index creation? My path to the plugin starts with my version of Lucene, so I expected my version to get priority.

TIA

+3
source share
3 answers

Seems to work now. For those of your interest, this is what I should have done:

  • Removed a piece of Lucene 1.4.3 from my plugin
  • I copied the old Lucene plugin from the old eclipse version to version 3.4.
  • Removed all dependencies in the plugin.xml wizard. Now all Lucene plugins are visible.
  • Selected version 1.4.xx and changed the properties to set the maximum version to 1.5
  • Other plugin dependencies added
  • Changed build path: removed old jar, add Lucene 1.4.3 plugin dependency
  • Recalculated startup configuration. The Lucene 1.4.3 plugin was not added automatically, so I added it manually.
  • Now that the index is generated, version 1.4.3 is loaded.

Hope this is useful to someone.

0
source

, ClassPath Checker ClassPath Helper .

, , , , , Luce .

ClasPath Checker:
classpath checker

(Obscured) Classpath: :
classpath helper

+3

Eclipse, OSGi. Eclipse OSGi, OSGi .

, Lucene , OSGi "-" "-Bundle", ; Lucene JAR . Lucene JAR, , , (, ).

- OSGI - OSGi ( OSGi Peter Kriens). - .

0

More articles:


All Articles