Community
Participate
Working Groups
In OSGiPlatformAbstraction line 84 is a log warning sent to the log service. When starting in Eclipse, this produces output DEBUG OUTPUT: false to the Eclipse log when not debugging. This should be removed or disabled so that by default no output is sent to the log when Eclipse is starting.
https://sourceforge.net/tracker/index.php?func=detail&aid=2007432&group_id=151721&atid=781930 Btw. if LogService is active during jSLP bundle startup, the stmt would be send there and not show up in the Eclipse Error log. ;)
(In reply to comment #1) > https://sourceforge.net/tracker/index.php?func=detail&aid=2007432&group_id=151721&atid=781930 > > Btw. if LogService is active during jSLP bundle startup, the stmt would be send > there and not show up in the Eclipse Error log. ;) > We don't have any control over the behavior of LogService in the Eclipse context...so I'm not sure what you are saying.
(In reply to comment #2) > We don't have any control over the behavior of LogService in the Eclipse > context...so I'm not sure what you are saying. It's meant as a workaround until we remove the debug stmt from jSLP and get a new CQ in.
...in scenarios where one has control over log service, e.g. in a RCP.
Setting target milestone and assigning to Markus.
Fixed in upstream (r243). Will hit ECF with a new CQ for jSLP.
Fixed in orbit