dir on command line does not override dir in build.js

[DashBDev]

I have a default dir specified in my build.js, but I sometimes override it on the command line.

In file:

dir: '../../build/temp'

Command line:

node r-1.0.5.js -o site\build.js  dir=../../build/temp2/

Both temp and temp2 directories are created. temp2 has all the files in an un-optimized state, temp has just a handful of files.
The optimizer errors with "No such file or directory '.../build/temp/xxx.js'"

This same config and command line works fine in 1.0.2.
I'm using node 0.6.9

[jrburke]

Thanks, looks like I goofed something there. I'll start a 1.0.6 release bucket because of this.

[jrburke]

I will track the fix over in r.js issue 94.

[DashBDev]

Thanks, this seems to work now. However, I notice that a relative dir on the command line seems to start from the current working directory whereas a relative dir in the build.js file is based off the location of the build.js file. Is this expected?

[jrburke]

Yes, that is the expected behavior for the "dir" config option.