| the test execution service launches additional JVM and Eclipse instance [message #86683] |
Wed, 08 November 2006 14:32  |
Eclipse User |
|
|
|
Originally posted by: ted.nospam.org
Hi,
The test execution service sample described in the documentation
(see belove)launches an additional JVM and Eclipse instance. This behaviour
is not the wanted when the test execution is launched from within an already
running Eclipse instance (e.g. from a plug-in). How can I configure the
test client adapter to not start a extra version of Eclipse?
/T
// Create the Java adapter associated with the specified Eclipse home
AutomationClientAdapter automation = new
AutomationClientAdapter("d:\\development\\eclipse");
// Create and configure a properties object
Properties properties = new Properties();
properties.setProperty("workspace", "D:\\development\\workspace");
properties.setProperty("project", "tests");
properties.setProperty("suite", "unit-tests/testA.testsuite");
// Execute the service named below using the configured properties
automation.execute("org.eclipse.hyades.test.tools.core.execute ",
properties);
|
|
|
|
| Re: the test execution service launches additional JVM and Eclipse instance [message #103915 is a reply to message #103829] |
Mon, 09 July 2007 20:12  |
 Joe Toomey
Messages: 79
Registered: July 2009 |
Member |
|
|
I think there are two issues in question here. The first issue (which
was fixed in TPTP 4.2) was that we launched an unnecessary additional
eclipse instance when running ASF services from outside of eclipse (in
order to change the workspace or VM arguments.) This has been corrected
in the OutOfProcessStrategy so now we launch the eclipse instance with
the correct workspace and VM args, thus eliminating the unnecessary JVM.
The second issue, which is what I believe Ted was asking about, is how
to use the current Eclipse/TPTP instance when invoking an ASF service
_from within an existing Eclipse/TPTP shell_. This behavior is
unchanged, and can be done easily by simply choosing the no-arg
constructor for the Java AutomationClientAdapter. The no-arg
constructor does not attempt to launch a new eclipse instance, and
instead invokes the service from within the existing Eclipse/TPTP instance.
Hope this helps,
--Joe
Paul Slauenwhite wrote:
> Hi Ted,
> This has since been fixed in 4.2. Please move up to the latest TPTP
> release:
>
> http://www.eclipse.org/tptp/home/downloads/?ver=4.4.0
>
> Paul
> "Ted" <ted@nospam.org> wrote in message
> news:eispqo$ojl$1@utils.eclipse.org...
>> Hi,
>> The test execution service sample described in the documentation
>> (see belove)launches an additional JVM and Eclipse instance. This
>> behaviour
>> is not the wanted when the test execution is launched from within an
>> already running Eclipse instance (e.g. from a plug-in). How can I
>> configure the
>> test client adapter to not start a extra version of Eclipse?
>>
>> /T
>>
>>
>> // Create the Java adapter associated with the specified Eclipse home
>> AutomationClientAdapter automation = new
>> AutomationClientAdapter("d:\\development\\eclipse");
>>
>> // Create and configure a properties object
>> Properties properties = new Properties();
>> properties.setProperty("workspace", "D:\\development\\workspace");
>> properties.setProperty("project", "tests");
>> properties.setProperty("suite", "unit-tests/testA.testsuite");
>>
>> // Execute the service named below using the configured properties
>> automation.execute("org.eclipse.hyades.test.tools.core.execute ",
>> properties);
>>
>>
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04032 seconds
] 
Search
Help
Register
Login
Home
