Hi, How about adding a hint to the docs stating that other bundles might be needed and that a list of dependencies can be found in the manifest.mf file of the scheduler bundle? I'd volunteer to adapt the docs (that I happen to draft with Carsten) accordingly but I'd need access rights for that :)
Cheers JC On Thu, Aug 5, 2010 at 1:14 PM, Mike Müller <[email protected]> wrote: > Hi > > Such depencies are reflected in the manifest.mf file of each > bundle. I don't think it's a good idea, to put them manually > into the documentation, as long as they can change over time. > > best regards > mike > > > -----Original Message----- > > From: Federico Paparoni [mailto:[email protected]] > > Sent: Thursday, August 05, 2010 10:04 AM > > To: [email protected] > > Subject: Re: Scheduler service problem > > > > > > 2010/8/5 Carsten Ziegeler <[email protected]> > > > > > Hi, > > > > > > the scheduler needs two other bundles: > > > > > > org.apache.commons.collections (which should be installed) > > > org.apache.sling.commons.threads 3.0.0 > > > > > > Regards > > > Carsten > > > > > > > > Now everything works, thanks. > > Anyway I think these informations should be available on the > > documentation ( > > http://sling.apache.org/site/scheduler-service-commons-schedul > er.html<http://sling.apache.org/site/scheduler-service-commons-schedul%0Aer.html> > ). > > -- > Federico >
