6

I'm trying to run a Powershell script without leaving Eclipse IDE so I setup External tool config as follows:

under "main" tab:

Location: C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe

Working Directory: C:\WINDOWS\system32\windowspowershell\v1.0\

Arguments: "& C:\PowershellScripts\script.ps1"

I save it and click run but nothing happens. A console window stays open diplaying C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe in title. I click on red Stop button but noting seems to happen anyway. The script is not exectued.

What am I missing?

Improve this question
2
  • found a workaround: location: C:\WINDOWS\system32\cmd.exe arguments: /c "powershell -file C:\Powershell\Script1.ps1" quotes are important. without them it will not execute the PS script. only thing remaining is to send the 'terminate' command somehow as the console window in eclipse doesn't terminate automatically. Commented Jan 7, 2010 at 18:32
  • Oh, it looks like you went the same route as me after some initial hiccups. As for "terminate automatically", I believe that the session would terminate as soon as you hit "enter". Commented Jan 7, 2010 at 18:41

3 Answers 3

Reset to default
7

I would probably use the -file argument, as in

-file "C:\PowershellScripts\script.ps1"

you may need to set the execution policy first if it's not already set to unrestricted on your system.

On my machine, a Windows 7 64-bit box with 64-bit Eclipse and a 64-bit jdk (1.6), I am able to get things to work if I set the "arguments" field to:

-executionpolicy unrestricted -file "c:\code\test.ps1"

An alternative that also worked for me was:

Set the application to launch as C:\Windows\System32\cmd.exe Set the arguments field to something like:

/c "powershell -executionpolicy unrestricted -file c:\code\test.ps1"

That does seem excessively Rube Goldbergian to me, but it's worth a try to see if your problems can be worked around by using a normal shell.

I did briefly get symptoms similar to what you describe, but I can't reproduce them anymore.

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

btw, you can pass the execution policy as an argument to powershell.exe
Yes, as -executionpolicy unrestricted, for example. (For some reason that didn't seem to work for me until I had changed the default policy at least once on my machine).
My execution policy is unrestricted. "-file"? It's not what the documentation mentions - technet.microsoft.com/en-us/library/ee176949.aspx#EBAA Anyway, even that doesn't work.
0

Your configuration actually worked for me with the additional -file parameter:

  • Location: C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe
  • Working Directory: C:\WINDOWS\system32\windowspowershell\v1.0\
  • Arguments: -file ${workspace_loc:/my-project/deploy.ps1}

Here I run the script even from within the Eclipse workspace.

Before I had to run a "PowerShell as Administrator" and run:

Set-ExecutionPolicy Unrestricted

That is shown here.

Improve this answer

2 Comments

Thanks for taking the time but how is this answer any different from the accepted answer?
You are right. Its basically the same. I wanted to point out that I manually set the execution policy in before. In addition it is shown how to run a file from within workspace.
0

The following argument solved everything for me:

-file "${resource_loc}"
Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.