Support for variables and variable files from command line
Originally submitted to Google Code by @yanne on 25 Jan 2009
It would be convenient to be able to define values for variables from command line. The values would not be replaced in the test data; instead their values could be used to try to resolve resource and variable file imports that contain variables.
Originally submitted to Google Code by @pekkaklarck on 26 Jan 2009
Actually these variables, and all other variables, should be used in when resolving imports. That would help fixing issue 69 .
Originally submitted to Google Code by @pekkaklarck on 26 Jan 2009
Support for variables in imports is issue 46 .
Originally submitted to Google Code by @yanne on 13 Mar 2009
Issue 114 has been merged into this issue.
Originally submitted to Google Code by Andreas.EbbertKarroum on 6 Jul 2010
What distance is the label "Target-Future" pointing at?
Originally submitted to Google Code by @pekkaklarck on 6 Jul 2010
Target-Future generally means post 1.0. Implementing this earlier is possible, though, especially if we get external help.
Originally submitted to Google Code by @jussimalinen on 6 Nov 2012
We decided not to implement this for now. We are happy to accept patches however.
Originally submitted to Google Code by @pekkaklarck on 10 Dec 2012
Issue 1149 has been merged into this issue.
Originally submitted to Google Code by @pekkaklarck on 10 Dec 2012
I can see this would be useful. Not too high priority though.