external tools and working directory problem

Hi I'm trying to config an external tool to run ant with this params:

program: ant

working directory: $Projectpath$/build

But it is not working as I was spect.

ant is not runing on build directory. It says /build does not exist

I don't understand why it is using global scope (/build) instead of doing ($Projectpath $/build).
I also try this:

working directory: $Projectpath$build

but it's even worse because it says /Applications/WebStorm.app/bin/build does not exist

I'm running a Mac

Any sugestions ??



I answer my self just in case anyone have the same problem

The problem results from GUI applications on MacOSX not using the same environment variables as those used by the terminal. As a result, the ‘npm’ or other command does not work when run from WebStorm, due to the ‘node’ path not being in the ‘PATH’ environment variable that WebStorm is looking at, even though it is in that of the terminal.

To solve this plroblem you can read this article witch explains the solution



I am hitting this problem/issue trying to create a tool to run browserify. Is there any chance it will be fixed? Is there a work-around?

This is the extent of the output when it fails:

C:\Users\ddurrett\AppData\Roaming\npm\browserify.cmd testMe.js > bundle.js
Error: Cannot find module 'C:\Users\ddurrett\projects\GroceryList\script\tmp\>' from 'C:\Users\ddurrett\projects\GroceryList\script\tmp'
    at C:\Users\ddurrett\AppData\Roaming\npm\node_modules\browserify\node_modules\resolve\lib\async.js:55:21
    at load (C:\Users\ddurrett\AppData\Roaming\npm\node_modules\browserify\node_modules\resolve\lib\async.js:69:43)
    at onex (C:\Users\ddurrett\AppData\Roaming\npm\node_modules\browserify\node_modules\resolve\lib\async.js:92:31)
    at C:\Users\ddurrett\AppData\Roaming\npm\node_modules\browserify\node_modules\resolve\lib\async.js:22:47
    at FSReqWrap.oncomplete (fs.js:99:15)

Process finished with exit code 1

Here is a screenshot of the settings I used to create this as an external tool:

external tools dialog.PNG
Is there something I've missed? The exact command works as expected when run from the same working directory as specified, with the parameters specified.

Please sign in to leave a comment.