9 Commits

Author	SHA1	Message	Date
Ewan Mellor	e90662ba10	Fix the AppVeyor tests. ... For some reason, possibly the new images that AppVeyor rolled out on Oct 22, our AppVeyor tests now fail immediately, with msbuild complaining that there are multiple solutions in the repository. Address this by not using the default AppVeyor build section, but calling msbuild ourselves explicitly in the build_script section. This way, we can specify which .slns we want to build. I have specified the runtime and runtime-testsuite Antlr4.vs2013.slns; the other ones didn't work for me in this configuration. Also, these builds were previously running with low / zero logging. As far as I can tell, this gave AppVeyor no way to know whether the build has succeeded or not. It certainly gives no way to diagnose any failures that do occur. I have dialed the logging up on everything. Also, remove the os declaration. That appears to be well out of date, and isn't on AppVeyor's list of images any more. I presume that we've been using their default image for some time.	2017-10-25 12:03:32 -07:00
Ewan Mellor	0097838b8a	Update AppVeyor version number to 4.7.1-SNAPSHOT.	2017-10-12 16:49:03 -07:00
Terence Parr	11bcd168fb	Update appveyor.yml	2016-11-21 14:40:46 -08:00
Terence Parr	d6f95111fc	Update appveyor.yml	2016-11-21 14:39:20 -08:00
Burt Harris	80a75894c8	eliminte trailing whitespace ... from last line of appvayor.yml	2016-09-26 15:37:50 -07:00
Burt Harris	7ebfabc175	Addomg verbosity: minimal fpr appveyor	2016-09-26 08:39:59 -07:00
Burt Harris	e71ebef3ec	Adding -q to mvn command line for appveyor	2016-09-26 08:28:52 -07:00
Burt Harris	7e2213dde7	appveyor.yml cpaitialization	2016-09-25 19:26:49 -07:00
Burt Harris	d9047112f5	Appveyor w/ semantic version	2016-09-25 16:53:27 -07:00