This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 23559 - -emacs not propagated to XTest instance
Summary: -emacs not propagated to XTest instance
Status: CLOSED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: xtest (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-15 18:09 UTC by Jesse Glick
Modified: 2003-07-02 12:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Portion of ant output (2.34 KB, text/plain)
2002-05-15 18:10 UTC, Jesse Glick 		Details
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 Jesse Glick 2002-05-15 18:09:47 UTC 
I run Ant with the -emacs flag, for use within
Emacs' M-x compile mode. This is fine.

But when I try to run XTest this way:

nice /space/ant14/bin/ant -emacs -f
/space/src/nb_all/xtest/instance/build.xml
cleantests buildtests runtests

it is not all that useful. The initial building of
xtest.jar honors the -emacs flag. But the real
work, including compilation of tests, does not,
and this looks bad and breaks hyperlinking in
Emacs. I guess a new Ant process is being
spawned?? See portion of log file.
Comment 1 Jesse Glick 2002-05-15 18:10:54 UTC 
Created attachment 5770 [details]
Portion of ant output
Comment 2 Martin Brehovsky 2002-05-15 18:29:12 UTC 
Yes, when running tests from instance, for each module is spawned new
ant process running in new JVM and only part of properties and
probably no flags are propagated to it.

We did it because of stability of xtest harness (prior to this change,
any module could cause xtest to crash, which is not acceptable when
running harness against nightly builds).
Comment 3 L Martinek 2002-06-18 14:06:59 UTC 
Module tests are spawned in new ant process. I can add parameter
-emacs to the new ant, but I cannot find out whether main ant process
was executed with -emacs. Moreover now output of each tested module
are redirected to file.
Comment 4 Jesse Glick 2002-06-18 15:26:06 UTC 
OK.
Comment 5 Quality Engineering 2003-07-02 12:20:09 UTC 
Resolved for 3.3.x or earlier, no new info since then -> verify.
Comment 6 Quality Engineering 2003-07-02 12:21:52 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.