Hi, my name’s Dave. This will likely sound backwards, but I’m migrating an Air
game with a node/js back-end from a heavier Jenkins/hudson/ant/svn build
process to a lighter-weight bash/git process in order to streamline devops for
a small team managing multiple game forks. I’m a Jenkins, ant,
Hi, my name’s Dave. This will likely sound backwards, but I’m migrating an Air
game with a node/js back-end from a heavier Jenkins/hudson/ant/svn build
process to a lighter-weight bash/git process in order to streamline devops for
a small team managing multiple game forks. I’m a Jenkins, ant,
It'
>
> I suspect that the opening single quote should be in a different location..
> Try putting it after the comma.
>
> - Josh
>
> On Mon, Nov 21, 2016 at 2:22 PM, Dave Taylor wrote:
>
>> Hi, my name’s Dave. This will likely sound backwards, but I’m migra
, at 3:00 PM, Josh Tynjala wrote:
>
> Why are you leaving the quote before -define? I meant that it was in the
> wrong place, so it should be removed from the start and put after the comma.
>
> -define=CONFIG::GAME_NAME,'A Name With Spaces In It'
>
> - Josh
>
&
.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0b
>> f69084-7abd.html
>>
>> I'm still pretty sure that you can omit your special bash quotes entirely
>> for this option. If they were required for string constants with spaces,
>> the examples in Adobe
