As part of our project builds, the intention is to use AStyle as a pre-build step to ensure proper code formatting. As AStyle only adjusts files that are not read-only; only files the user has checked out our touched, which is the desired behavior. Once all code is checked in however, all files are read-only, and the pre-build step fails, which fails the build. We have modified the source to work around this issue locally.
Would you consider, either a) removing the error condition when no files are found to modify. or b) removing the error condition for the more specific case where only read-only files were found.
Ticket moved from /p/astyle/bugs/187/
The next release will have
--accept-empty-listto no longer exit with error status in this caseNew release 3.6.5 is available