Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 2.1.0

Bug #13330 Output non-content-warnings on stderr
Submitted: 2008-03-07 07:21 UTC Modified: 2008-03-19 22:11 UTC
From: temp Assigned: squiz
Status: Closed Package: PHP_CodeSniffer (version 1.0.1)
PHP Version: 5.2.5 OS:
Roadmaps: 1.1.0    
Subscription  


 [2008-03-07 07:21 UTC] temp (Stephan Wentz)
Description: ------------ When using the Zend Standard without the Zend Code Analyer path set, phpcs generated a warning for each file that is being checked. Combined with the xml renderer and redirecting the output to a file results in a not-valid xml document. Maybe the warnings that are no content-warnings (like the missing Zend Code Analyzer) should be output' to stderr, not stdout. Then you would see the warnings, but if you redirect to a file these warnings wouldn't get saved. Test script: --------------- - Expected result: ---------------- valid XML file Actual result: -------------- invalid XML file

Comments

 [2008-03-07 15:37 UTC] squiz (Greg Sherwood)
Thank you for taking the time to report a problem with the package. This problem may have been already fixed by a previous change that is in the CVS of the package. Please log into CVS with: cvs -d :pserver:cvsread@cvs.php.net:/repository login and check out the CVS repository of this package and upgrade cvs -d :pserver:cvsread@cvs.php.net:/repository co pear/PHP_CodeSniffer pear upgrade pear/PHP_CodeSniffer/package2.xml or pear upgrade pear/PHP_CodeSniffer/package.xml If you are able to reproduce the bug with the latest CVS, please change the status back to "Open". Again, thank you for your continued support of PEAR. I've removed that warning in the CVS version.