[
https://issues.apache.org/jira/browse/KARAF-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209388#comment-13209388
]
Chris Dolan commented on KARAF-1199:
------------------------------------
Guillaume, I think dev:watch is different from osgi:list because dev:watch has
a persistent asynchronous component (the BundleWatcher) whereas osgi:list is
purely synchronous. I'm proposing only that the background thread BundleWatcher
message is emitted as a log message, not the synchronous output of dev:watch.
I'd be happy if the BundleWatcher message were emitted to both logging and
console. But, yes, this is not for production which is why I marked it
"trivial".
> dev:watch command issues "[WATCH]" announcements only to the issuing shell
> --------------------------------------------------------------------------
>
> Key: KARAF-1199
> URL: https://issues.apache.org/jira/browse/KARAF-1199
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 2.2.4
> Reporter: Chris Dolan
> Assignee: Jean-Baptiste Onofré
> Priority: Trivial
> Fix For: 2.2.6, 3.0.0
>
>
> If I issue a "dev:watch *" command and later update one of my snapshot
> bundles, the announcement of that change is emitted in the context of the
> shell that issued the command. That is, if I issue it in the Gogo ssh shell,
> then the "[WATCH] ..." announcement goes to that shell. If I trigger the
> Watch service programmatically, then the announcement goes to the system
> console.
> Instead, I think the announcement should go to the log subsystem. The root
> cause is that org.apache.karaf.shell.dev.BundleWatcher uses
> System.out.println() to emit this message, which is routed by Gogo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
