Description: ------------ After running docblockgen, even though it sorts out the spacing, it doesn't fix the ordering outlined by PHP_CodeSniffer. eg: The @license tag is in the wrong order; the tag follows @copyright (if used) or @author The @copyright tag is in the wrong order; the tag follows @author The @link tag is in the wrong order; the tag follows @version ...

To reproduce these errors, you need to do the following: Get Compat.php from the PHP_Compat package. Run: docblockgen Compat.php Compat.phps This should create a new file called Compat.phps Diff Compat.php and Compat.phps and you should be able to see the spacing is sorted. Run: phpcs --standard=PEAR Compat.phps It should tell you that the "tags" are in the wrong order. eg: 11 | ERROR | The @license tag is in the wrong order; the tag follows | | @copyright (if used) or @author 12 | ERROR | The @copyright tag is in the wrong order; the tag follows | | @author 13 | ERROR | The @version tag is in the wrong order; the tag follows | | @license The result would be similar to the Align.php which appears to deal with aligning, but not ordering.

To reproduce these errors, you need to do the following: Get Compat.php from the PHP_Compat package. Run: docblockgen Compat.php Compat.phps This should create a new file called Compat.phps Diff Compat.php and Compat.phps and you should be able to see the spacing is sorted. Run: phpcs --standard=PEAR Compat.phps It should tell you that the "tags" are in the wrong order. eg: 11 | ERROR | The @license tag is in the wrong order; the tag follows | | @copyright (if used) or @author 12 | ERROR | The @copyright tag is in the wrong order; the tag follows | | @author 13 | ERROR | The @version tag is in the wrong order; the tag follows | | @license The result would be similar to the Align.php which appears to deal with spacing, but not ordering.

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.

test