Hi Gert,
For the head/tail command, for sure, it can be helpful. I added
log:clear to avoid to get too larger log displayed.
OK to raise a Jira to add head/tail "util" commands in addition of the
grep one.
For the second point, maybe we can set a kind of development mode to
periodically watch no updated bundle. I don't think that putting this
behavior in the bundle URL is interesting because most of the time,
users will forget to set it.
I'm more for a kind of etc/org.apache.karaf.deployer.cfg switching
development mode. The configuration file could contain the watching
interval, a watching filter (to exclude some bundle), etc.
Like this, a production karaf instance will disable it and it's easy to
switch on using just this configuration file. The feature descriptor and
bundles URI are not changed.
Regards
JB
On 12/06/2010 02:59 PM, Gert Vanthienen wrote:
L.S.,
Last week, I was having a chat with some local Karaf/Camel/ServiceMix
users. During the conversation, they came up with a few fair requests
for new features to be added to Karaf:
- a head and tail utility for limiting output on some commands
- a way to watch a bundle location for changes after installation -
e.g. when doing development, a way to trigger file-install to monitor
a mvn: url for changes to automatically update a bundle as soon as a
new snapshot has been built (something like a osgi:install -s
watch:<original uri> perhaps)?
Wdyt? I'll gladly raise the JIRA issues afterwards, but I wanted to
get some feedback first.
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
