On 1/29/10 13:19, Joel Schuster wrote:
Oh, wait. After re-reading I believe you are saying I should implement that
functionality... You know, contribute.
Yes, that is what I was saying. There is currently no support for that.
I don't know the File Install code really well, but I believe that it
allows you to configure new directories by dropping in a .cfg file to
configure new watched directories. So, it would seem one would just need
to modify File Install to introduce a new config property for setting a
bundle's start level once it is installed. This should be fairly
straightforward especially seeing that File Install already tracks the
Start Level service.
Of course, I am not a user of File Install, so maybe there are reasons
why not to do this. At a minimum, open a JIRA issue and request the feature.
-> richard
-----Original Message-----
From: Joel Schuster [mailto:[email protected]]
Sent: Friday, January 29, 2010 11:14 AM
To: [email protected]
Subject: RE: FileInstall at different start levels
How would I associate a default start level config property per directory. This
sounds like exactly what I need, just not sure how that would work in practice.
- Joel
-----Original Message-----
From: Richard S. Hall [mailto:[email protected]]
Sent: Friday, January 29, 2010 11:12 AM
To: [email protected]
Subject: Re: FileInstall at different start levels
On 1/29/10 13:00, Joel Schuster wrote:
Is there any way to have multiple different FileInstall instances have
different start levels?
I'm using FileInstall with multiple cfgs (up to 10), each monitoring different
bundle/config directories depending on how I need to configure my run time.
I'm running into cases where one set needs to be all started before another set
of bundles come up.
Any suggestions?
Currently, I don't think File Install deals with bundle start levels at all.
One way to support this is to associate a default start level config
property per watched directory, so the bundles in that directory would
be put into the specified start level. You could create an issue and/or
submit a patch...
-> richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
