Hey Guys:
Can you clarify how you guys call filesystem commands like npm and cordova?
In the CDK tools as currently coded, we do two different things. One, is that we create an "External Tools Launch Configuration" which runs the command. This requires knowing the actual location of the executable. The other is to simply call Runtime.exec(etc) and get a Process from it.
The external tools launch config is useful because it opens a console for us and means we don't have to do any of the wiring, so we use that when we know we want the commands to be visible to the user. We use the runtime.exec() in the background for commands that we want to run without showing the user (for example if we did a vagrant adbinfo)
How do you all do it?
- Rob Stryker
On 12/03/2015 11:36 AM, Max Rydahl Andersen wrote:
Can you clarify how you guys call filesystem commands like npm and cordova?
In the CDK tools as currently coded, we do two different things. One, is that we create an "External Tools Launch Configuration" which runs the command. This requires knowing the actual location of the executable. The other is to simply call Runtime.exec(etc) and get a Process from it.
The external tools launch config is useful because it opens a console for us and means we don't have to do any of the wiring, so we use that when we know we want the commands to be visible to the user. We use the runtime.exec() in the background for commands that we want to run without showing the user (for example if we did a vagrant adbinfo)
How do you all do it?
- Rob Stryker
On 12/03/2015 11:36 AM, Max Rydahl Andersen wrote:
> public static String getVagrantLocation() { > - return VAGRANT_LOCATION_LINUX; > + return findVagrantLocation();im wondering if we are better of launching this similar to what @gercan and @ibuziuk been doing for npm and cordova cli tools.
i.e. call out via bash or cmd.exe making it up to the user to have it properly configured in PATH
—
Reply to this email directly or view it on GitHub.
