172472 – [external tools][resolver] External tools don't work with Windows Services for UNIX tools

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 172472 - [external tools][resolver] External tools don't work with Windows Services for UNIX tools

Summary: [external tools][resolver] External tools don't work with Windows Services fo...

Status:	CLOSED DUPLICATE of bug 255619

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Debug (show other bugs)
Version:	3.2.1
Hardware:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-Debug-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-02-01 07:54 EST by Graeme Harker
Modified:	2011-06-06 13:10 EDT (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Graeme Harker

2007-02-01 07:54:59 EST

Build ID: M20060921-0945

Steps To Reproduce:
1. Install bundled Eclipse 3.2 with WTP 1.5.1 on Windows XP Pro SP2
2. Install Microsoft Windows Services for UNIX (v8.0.1969.1) http://www.microsoft.com/technet/interopmigration/unix/sfu/default.mspx
(like Cygwin but from Microsoft)
3. "External Tools" -> "Program" -> "New", 
4. Set Location: c:\SFU\bin\tail
5. Set Arguments: -f ${resource_loc} (or -f "${resource_loc}")
6. Run

More information:
You get tail: Could not open file 'C:\Projects\Eclipse 3.2 with Flex 2.0.1\TestNewFdsProject\logs\main.log': No such file or directory

Comment 1 Darin Wright

2007-05-17 15:21:01 EDT

Does the tool work from the command line when a file with spaces is specified? Other tools work fine - for example, NotePad.exe.

Comment 2 Graeme Harker

2007-05-17 15:30:33 EDT

C:\> tail -f "C:\Projects\Eclipse 3.2 with Flex 2.0.1\TestNewFdsProject\logs\main.log"

works fine from the command line.

The problem is that Eclipse external tools appears to strip the " in "${resource_loc}" before the path reaches Windows.

Comment 3 Michael Rennie

2011-06-06 13:10:42 EDT

Looks like the same problem as bug 255619 - we are mis-handling quotes when resolving the variable. Marking as a dupe of bug 255619 since that bug has a proposed fix on it.

*** This bug has been marked as a duplicate of bug 255619 ***