On 8/5/09 16:41, Richard S. Hall wrote:
On 8/5/09 16:31, Marcel Offermans wrote:
Ok, update does not get in the way of some other "management agent"
so if you make that a switch (so I don't have a longer startup time
because the framework is updating all bundles on every launch) then
that's fine!
True, it could result in longer startup times since I just implemented
it in a very simple way...I always update whether it is needed or not.
I did this since it was much simpler than trying to detect
modification times and somehow saving that data for the next
execution. A switch to enable/disable this would be fine.
I see Felix' launcher as a simple tool to help bundle developers use
the framework. I don't see the launcher as a valuable tool to be used
for launching and provisioning real systems.
So, for me, these changes are really to help developers using Felix
during development, but still we could make a switch to control it.
Actually, I had an idea which could make all of it possible if we are
going to introduce a configuration switch. Make the switch like this:
felix.auto.deploy.action=<comma-delimited-actions>
Where possible actions include "install", "start", "update", and
"uninstall". The default value would be "install,start,update".
This way, people could customize the behavior to their specific needs
and it would still be easy to implement.
Thoughts?
-> richard
