Uh oh!
There was an error while loading. Please reload this page.
Remove console output from AppiumDriverLocalService by default - #483
Remove console output from AppiumDriverLocalService by default#483Mygod wants to merge 2 commits into
Conversation
Reason: I need to use System.out to print some less verbose output. And users can easily turn it back on by calling addOutPutStream anyway.
alexander-poulikakos
commented
Nov 24, 2016
I fully agree on this PR. We should not log to System.out by default. |
SrinivasanTarget
commented
Nov 28, 2016
@TikhomirovSergey ping |
jeangb
commented
Feb 16, 2017
Hi, this looks very interesting. |
Mygod
commented
Feb 20, 2017
@jeangb Meanwhile you can still use the workaround mentioned in the PR to get rid of the console output. |
jeangb
commented
Feb 20, 2017
Thank you @Mygod, in what class this workaround take place ? |
Mygod
commented
Feb 20, 2017
@jeangb Just whenever you create a |
jeangb
commented
Feb 20, 2017
@Mygod great, thx |
selenUser
commented
Feb 20, 2017
@Mygod which type is |
Mygod
commented
Feb 20, 2017
It's a Field in reflection. :) |
drapostolos
commented
Feb 20, 2017
Perhaps this can be merged to master and released? To avoid workarounds... |
jeangb
commented
Feb 20, 2017
Do you think it would be possible to redirect this stream to an other view that console, in Eclipse. For example this view could be called Server. |
- Workaround until this appium/java-client#483
VenkateshPS
commented
Jan 22, 2018
Thanks @Mygod the workaround saved me. |
mykola-mokhnach
commented
May 24, 2018
Prasannajnaeyulu
commented
Jun 19, 2019
This is where one can find the workaround until the appium server with this changes is released |
Change list
Remove console output from AppiumDriverLocalService by default.
Types of changes
Details
Reason: I need to use
System.outto print some less verbose output. And user can easily turn it back on by callingaddOutPutStream.However the other way around is hard. Here's what I'm currently using.