Hi, On Fri, Jul 6, 2012 at 7:47 PM, Kevin Milburn <[email protected]> wrote: > Eclipse is a finicky beast, even if a bundle has an Activator it won't be > activated if the Bundle-ActivationPolicy is not set, unless the product is > modified to explicitly auto start the bundle.
Interesting, I didn't know that. > Ideally, it would be preferable to set the Bundle-ActivationPolicy to lazy > to allow Eclipse (and others?) to do the right thing without needless > complication. Sounds like a good idea! > 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. > p.s. an alternative method of obtaining access to the Detector and Parser > involves something like this in your own bundles activator: The reason why we use ServiceTrackers instead is that we want to support deployments where new parser and detector services can be added or removed dynamically from the running system. BR, Jukka Zitting
