From 1140679d8f1f81bd83b6cd2b724518e7d0310921 Mon Sep 17 00:00:00 2001
From: Rob Reynolds <ferventcoder@gmail.com>
Date: Sat, 9 Apr 2016 14:12:39 -0500
Subject: [PATCH] (GH-571) Arg parsing error should be warning

Instead of logging a debug message, argument parsing errors should be
reported as warnings in case the argument doesn't actually evaluate
appropriately later.
---
 src/chocolatey/infrastructure/commandline/Options.cs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/chocolatey/infrastructure/commandline/Options.cs b/src/chocolatey/infrastructure/commandline/Options.cs
index 6a4aa3ef87..e71dd4b6e2 100644
--- a/src/chocolatey/infrastructure/commandline/Options.cs
+++ b/src/chocolatey/infrastructure/commandline/Options.cs
@@ -824,7 +824,7 @@ protected virtual bool Parse (string argument, OptionContext c)
 		    }
 		    catch (Exception ex)
 		    {
-                "chocolatey".Log().Debug("Parsing {0} resulted in exception:{1} {2}".format_with(argument,Environment.NewLine,ex.Message));
+                "chocolatey".Log().Warn("Parsing {0} resulted in exception:{1} {2}".format_with(argument, Environment.NewLine, ex.Message));
 		    }
             
 			return false;