There are a several situations that exist where Buildtools exits without actually building anything. This is expected, but in these cases it should exit with a non-success (or non-zero) stop code.

As of right now, Buildtools is actually pretty good about this. However, there are still some situations right now that exit with a status of zero despite not doing anything. Namely, when the user runs Buildtools incorrectly.

I have identified the following ways to get a success code (0) from buildtools despite not building anything:

• Run Buildtools in a folder named "#server"
• Run Buildtools in a folder named "OneDrive"
• Attempt to build a server version that doesn't exist ("1.99.7" for example)

To see this yourself, launch Buildtools in this fashion: (Bash)

java -jar BuildTools.jar --rev 1.99.7; echo Stop Code: $?