Description Corey Ashford 2011-08-22 19:02:49 EDT

Build Identifier: I20110613-1736  PTP 5.0.2

ETFw checks for the existence of the tool specified by the command attribute of the utility element in the .xml file by attempting to open it using File(String).

This does not work for remotely-located tools.

The only way to work around this that I'm aware of is to add a utility which uses the "internal" group, which can then call a Java class method, which would then do the remote launch based on the information it finds in the launch config that is passed to it.

Reproducible: Always

Steps to Reproduce:
To see one location in the ETFw source code where the assumption of the tool being
located on the local machine, look at:

org.eclipse.ptp.etfw.internal.LauncherTool (starting at line 157):

	// String
	// util1Path=BuildLaunchUtils.checkToolEnvPath(firstExecUtil);
	File f = new File(firstExecUtil);
	if (firstExecUtil == null || !f.exists())
		throw new Exception(Messages.LauncherTool_Tool
 		firstExecUtil + Messages.LauncherTool_NotFound);