savoytruffle:app bhatfield$ alloy generate jmk
fs.js:338
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: ENOENT, no such file or directory '/Users/bhatfield/practice/testalloy/app/app/alloy.jmk'
at Object.fs.openSync (fs.js:338:18)
at Object.fs.writeFileSync (fs.js:756:15)
at module.exports (/usr/local/lib/node_modules/alloy/Alloy/commands/generate/targets/jmk.js:18:5)
at generate (/usr/local/lib/node_modules/alloy/Alloy/commands/generate/index.js:38:34)
at Object.<anonymous> (/usr/local/lib/node_modules/alloy/Alloy/alloy.js:81:46)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:362:17)
at require (module.js:378:17)
at Object.<anonymous> (/usr/local/lib/node_modules/alloy/bin/alloy:3:1)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.runMain (module.js:492:10)
at process.startup.processNextTick.process._tickCallback (node.js:244:9)
I can get the command to work if I specify the -p option. I can generate the other components (views, widgets, controllers, etc.) fine without specifying the -p option.