On 2012/07/06 22:31, Jukka Zitting wrote:
On Fri, Jul 6, 2012 at 7:47 PM, Kevin Milburn
<[email protected]> wrote:
I've tested this by modifying the tika-core/pom.xml (see attached), and
adding the following line:
<Bundle-Activator>
org.apache.tika.config.TikaActivator
</Bundle-Activator>
+ <Bundle-ActivationPolicy>lazy</Bundle-ActivationPolicy>
Any chance of this for the 1.2 release?
Sure, I just committed it, see https://issues.apache.org/jira/browse/TIKA-951.
Thanks for that, I've tested the latest snapshot (and RC1) and things
behave themselves a lot better.
It would be nice if the Tika and TikaConfig classes had greater
awareness of the OSGI environment as they currently perform redundant
work trying to load the services files which they'll never find.
Thanks again
Kevin.
p.s. For those trying to get Tika to work in Eclipse, you need to do
something along these lines.
Change the Target Definition (or create a new one)
On the Definition tab, add the location of the tika-bundle and
tika-core jars
On the Content tab, make sure the core and bundle plugins are
selected
Set as Target Platform
In each plugin that needs Tika support, add org.apache.tika.core to the
plugins dependencies
Change the Product Configuration (or create a new one),
On the Dependencies tab, add org.apache.tika.core and o.a.t.bundle
On the Configuration tab, add o.a.t.bundle to the Start levels,
and set Auto-Start to true.
On the Overview tab, Test the product by launching a runtime
instance of it.
