Do you have the JAR files in classpath or do you extract them and merge all class files and resources? This happens, e.g. if you ask Eclipse to create one uber-jar containing everything. The problem that then appears is, that every meta-inf file coming from separate jar files are overwriting each over. SPI is relying on actual jar packages as deployment units.
If you only add the unmodified jar files to classpath, this should work. The same applies by the way for Solr and Lucene 4.0, which also use SPI for their codec infrastructure. ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Kevin Milburn [mailto:kmilb...@gpslsolutions.com] > Sent: Thursday, July 05, 2012 7:11 PM > To: user@tika.apache.org > Subject: using tika with eclipse > > Hi > > I've been trying to add tika 1.1 support to an Eclipse RCP application but am > struggling to get the parsers loaded. > I have both tika-core-1.1.jar and tika-bundle-1.1.jar plugins added to the target > and selected within product and have confirmed both plugins are present in the > running program. > > The fundamental problem appears to be that the TikaConfig is ultimately > reaching ServiceLoader.findServiceResources, looking for > META-INF/services/org.apache.tika.parser.Parser. While doing so, it > only appears to check the org.apache.tika.core plugin, it doesn't contain it, so > not Parsers are available. > > Any ideas where I may have gone wrong or how to get it working? > > TIA > Kevin.
