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 36725 - External Execution does not save "enable asserts" value
Summary: External Execution does not save "enable asserts" value
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Pokorsky
URL:
Keywords: SIMPLEFIX
Depends on:
Blocks:
 
Reported: 2003-10-21 16:46 UTC by _ gtzabari
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

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 _ gtzabari 2003-10-21 16:46:34 UTC 
dev build 200307280100
Sun JDK 1.4.1_01

Options | Editing | Java Sources | External
Execution | Enable Asserts | Set to true

Then close the options dialog and shutdown Netbeans

Restart Netbeans, notice the "Enable Asserts"
value was reset to false. I'm expecting Netbeans
to retain my settings.
Comment 1 _ gtzabari 2003-12-31 06:28:26 UTC 
Marek,

   Looks like a simple bug, can you please take a look at it?
Comment 2 mslama 2004-01-08 16:54:05 UTC 
I will check but I do not think core/ui is responsible for persistence
of some settings.
Comment 3 Petr Nejedly 2004-02-26 13:05:09 UTC 
Although I can't reproduce the problem (the setting is correctly
persisted for me), I must admit that it shouldn't work.
In JavaProcessExecutor, the setAssertEnabled method doesn't fire a
propChange. And yes, it should be SIMPLEFIX
Comment 4 Jan Pokorsky 2004-02-26 13:40:58 UTC 
I can. You have to exactly follow steps in the options dialog
described by Gili.
Comment 5 Jan Pokorsky 2004-02-26 13:41:47 UTC 
fixed in

/cvs/java/src/org/netbeans/modules/java/JavaProcessExecutor.java,v1.14