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

Bug 355448

Summary:	ETFw doesn't handle launching remote tools (a.k.a. utility / utilities and commands)
Product:	[Tools] PTP	Reporter:	Corey Ashford <cjashfor>
Component:	ETFw	Assignee:	Wyatt Spear <wspear>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	wspear
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

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);

Comment 1 Corey Ashford

2011-08-31 18:57:27 EDT

Wyatt, I hope you don't mind me adding you to the cc list on this bug.  I think you might be interested in this.

Comment 2 Greg Watson

2012-05-25 13:34:20 EDT

Is this still the case, or has this been fixed?

Comment 3 Wyatt Spear

2012-09-21 18:01:52 EDT

Remote launching and workflow control is now supported.  However use of groups and local control of tool paths is not available for remote ETFw launches.