Description
When a build fails in the MSBuild phase the errors are logged in the CLI at the warn level see below for an example
[WARN] C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(2247,9): error APPX0105: Cannot import the key file 'C:\Users\Windo_000\Documents\Appcelerator_Studio_Workspace\classicProject\generated.pfx'. The key file may be password protected. To correct this, try to import the certificate manually into the current user's personal certificate store. [C:\Users\Windo_000\AppData\Local\Temp\classicPro
ject\store.x86\ClassicProject.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(2247,9): error APPX0102: A certificate with thumbprint 'undefined' that is specified in the project cannot be found in the certificate store. Please specify a valid thumbprint in the projec
t file. [C:\Users\Windo_000\AppData\Local\Temp\classicProject\store.x86\ClassicProject.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(2247,9): error APPX0107: The certificate specified is not valid for signing. For more information about valid certificates, see http://go.microsoft.com/fwlink/?LinkID=241478. [C:\Users\Wind
o_000\AppData\Local\Temp\classicProject\store.x86\ClassicProject.vcxproj]
Errors should be surfaced to the error level of logging
Steps to reproduce
1. Build a project using appc run -p windows -T ws-local
2. Either provide a cert of generate one, when entering the password enter an incorrect password
Actual result
The build will error and the errors will be surfaced to the warn log level
Expected result
The errors should surface to the error log level
PR: https://github.com/appcelerator/titanium_mobile_windows/pull/392
Verified using: Windows 8.1 Appc CLI Core: 5.0.0-33 Appc CLI NPM: 4.2.0-1 Titanium SDK: 5.0.0.v20150902095518 Errors from MSBuild are now thrown at the error level
Closing ticket