[GitHub] [commons-imaging] kinow commented on pull request #35: IMAGING-154 Removed Debug class

["kinow (via GitHub)" <gi...@apache.org>]

kinow commented on PR #35:
URL: https://github.com/apache/commons-imaging/pull/35#issuecomment-1605927366

   >So, what is the code migration path for ImagingConstants.PARAM_KEY_VERBOSE? In other words, how should we turn on some sort of file parser debug logging?
   
   We are using `java.util.logging`, JUL. You can tweak the logging level to see the messages that were previously written to the stdout when the `PARAM_KEY_VERBOSE` was enabled.
   
   https://commons.apache.org/proper/commons-imaging/gettingstarted.html (see Logging)
   
   >I am asking because every now and then we have to deal with non‑compliant JPEG files and we would like to get some clue or provide some info to the user that a file is broken.
   
   Could you try the JUL and let us know if it contains enough info to tell users what is wrong when reading or parsing the JPEG files, please? If there's anything lacking, feel free to open an issue and maybe point at what could be improved (e.g. number of segments, stage of parsing where it failed parsing, etc.)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@commons.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org