[
https://issues.apache.org/jira/browse/KARAF-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209234#comment-13209234
]
Guillaume Nodet commented on KARAF-1199:
----------------------------------------
Well, I somewhat disagree with that.
The original idea of the dev:watch command was to be a developer tool, not
something to use in production.
Likewise, the osgi:list command does not output to the log system instead of
the console.
I guess this should be configurable when launching the command, but I'd like to
keep the current behavior which is a really nice tool when developing. Though
even if the command output to the console, it'd be nice to have it log the
changes anyway.
> 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
