Log level should be changed to INFO

[GoogleCodeExporter]

When I use JODConverter library there are some log message with ERROR level, 
but they should be changed to INFO because are not errors but info messages:

10:47:31,421 ERROR [STDERR] 18-nov-2010 10:47:31 
org.artofsolving.jodconverter.office.ProcessPoolOfficeManager <init>
INFO: ProcessManager implementation is WindowsProcessManager
10:47:32,343 ERROR [STDERR] 18-nov-2010 10:47:32 
org.artofsolving.jodconverter.office.OfficeProcess start
INFO: starting process with acceptString 
'socket,host=127.0.0.1,port=2002,tcpNoDelay=1' and profileDir 
'C:\Users\xxxxx\AppData\Local\Temp\.jodconverter_socket_host-127.0.0.1_port-2002
'
10:47:33,026 ERROR [STDERR] 18-nov-2010 10:47:33 
org.artofsolving.jodconverter.office.OfficeProcess start
INFO: started process; pid = 3736
10:47:35,035 ERROR [STDERR] 18-nov-2010 10:47:35 
org.artofsolving.jodconverter.office.OfficeConnection connect
INFO: connected: 'socket,host=127.0.0.1,port=2002,tcpNoDelay=1'

Original issue reported on code.google.com by monk...@gmail.com on 19 Nov 2010 at 11:47

[GoogleCodeExporter]

Version: 3.0-beta-3

Original comment by monk...@gmail.com on 19 Nov 2010 at 11:51

[GoogleCodeExporter]

Log level *is* already INFO as you can see from the lines you pasted e.g. 
"INFO: connected". Why java.util.logging goes to STDERR and then relogged as 
ERROR I have no idea, must depend on how it's configured in your own app.

Original comment by mirko.na...@gmail.com on 12 Mar 2011 at 5:18

• Changed state: Invalid

[GoogleCodeExporter]

After some research, I discovered the real problem: JodConverted was using a 
different Java Loggin solution. And the solution was fount at 
http://shrubbery.mynetgear.net/c/display/W/Routing+java.util.logging+messages+to
+Log4J.

I need to use http://www.slf4j.org/api/org/slf4j/bridge/SLF4JBridgeHandler.html 
to redirect all JUL log records are redirected to the SLF4J API.

Original comment by monk...@gmail.com on 14 Mar 2011 at 9:39