Russel Winder wrote:
On Tue, 2009-08-18 at 11:59 +1000, Adam Murdoch wrote:
The ^ prefix doesn't work on windows. It just goes missing. Bah.
Is this true generally or just for your one case?
I don't know. I couldn't find any decent reference material (not that I
tried very hard). The ^ character is a reserved character for batch
scripts in some way.
I tried a few experiments and couldn't convince windows to pass the ^
through to the gradle script.
I'm going to switch to a trailing - character for now, to get the broken
windows build to pass.
I am not sure that will work as well as you hope. Commands are read
left-to-right and people generally stop reading the word when they have
recognized it and they move on to the next word. This means ends of
words are often not read in the same detail as the beginning of a word.
Trailing - could get lost.
Maybe. People write the command-lines much, much more often than they
read them, so I'm not sure it's much of a problem.
I was going to suggest a character such as @
or # -- something big, preferably used at the start as you were trying
with ! and ^.
The problem with # is that it is used as the comment character in
scripts so might present a problem. I haven't experimented.
It seems to me that any useful punctuation character, other than '-', is
pretty much taken already.
An alternative might be to use a command-line option for excluding tasks:
gradle developerBuild -x test -x check
gradle developerBuild -x test,check
Having used the nnn- format for a few days, I'm pretty happy with it. It
works ok. And the behaviour is so very much better than the old
-Dskip.nnn behaviour.
Adam
