jcricket/gwt-syncproxy

Prints a warning to standard error

Closed this issue · 4 comments

What steps will reproduce the problem?
1.Use sync proxy with a class that does not have a serialization policy
2.See the warning printed to standard error
3.

I am using this in a CLI and do not want anything going to standard error other 
than what I write to standard error

What is the expected output? What do you see instead?
The expect output would be nothing.  I expect this to go to a log that can be 
controlled.

What version of the product are you using? On what operating system?
0.31

Please provide any additional information below.
I have a quick fix that routes the warning to a logger instead of standard 
error.

Contact me
brian.mason@netapp.com

Original issue reported on code.google.com by f64ph...@gmail.com on 18 Oct 2012 at 2:00

The next release will be utilizing util.Logger for all appropriate information 
for both POJ and Android systems(LogCat).

Original comment by p.pr...@blueesoteric.com on 29 Dec 2014 at 3:10

  • Changed state: Started

Original comment by p.pr...@blueesoteric.com on 29 Dec 2014 at 3:16

Removal of System printouts from the gwt-syncproxy and Android library core and 
conversion to Java Util logging completed.

Original comment by p.pr...@blueesoteric.com on 2 Jan 2015 at 2:10

  • Changed state: CompletePending
  • Added labels: Milestone-Release0.5
SyncProxy library version 0.5 is now available

Original comment by p.pr...@blueesoteric.com on 11 Jan 2015 at 4:32

  • Changed state: Fixed