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.
Summary: | [68cat] java.beans.PropertyVetoException: Not allowed | ||
---|---|---|---|
Product: | utilities | Reporter: | giorgio42 <giorgio42> |
Component: | Properties | Assignee: | Victor Vasilyev <vvg> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | aldobrucale, blaha, georges, mmirilovic, mslama, ulfzibis |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=160700 | ||
Issue Type: | DEFECT | Exception Reporter: | 160700 |
Attachments: |
stacktrace
stacktrace stacktrace stacktrace |
Description
giorgio42
2009-10-23 11:17:54 UTC
Created attachment 89971 [details]
stacktrace
This issue already has 12 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=160700 Again in IDE log: INFO [org.openide.text.CloneableEditorSupport]: callNotifyModified notifyModified returns false this:org.netbeans.modules.properties.PropertiesEditorSupport Please evaluate. Created attachment 91621 [details]
stacktrace
It is regression after a fix of the bug 89029. http://hg.netbeans.org/main/rev/6f190c73dac1 The true value should be returned in the method notifyModified() of the class org.netbeans.modules.properties.PropertiesEditorSupport after a successful saving of a properties file. Moreover, the flag "modified" is false after the saving, but it should have the true value and all titles of the tabs for the property file under modification should be updated. Therefore, super.notifyModified() should be called again after saving. Fixed in the main trunk http://hg.netbeans.org/main/rev/72542a8aaa77 *** Bug 174414 has been marked as a duplicate of this bug. *** Created attachment 92558 [details]
stacktrace
Created attachment 93307 [details]
stacktrace
Any idea why this fix has not bee included in the first set of patches for NB 6.8 ? It makes the "diff to" functionality a lot less valuable (in other words, is a royal pain in the ass...). As the bug has not been fixed in 6.8 patch1 I am reopening it (never claim to have fixed a bug unless it is included in an official release or patch). Sorry for the inconvenience. Please check patch nomination process: http://wiki.netbeans.org/NetBeansPatchesProcess This bug is fixed in the 6.9 development with target milestone set to 6.9 Yes, but you have not yet delivered this bug to the customer. Now whenenver I submit this exception to the exception reporter it tells me that the bug has already been fixed, but (from the customer perspective) this is simply wrong and really confusing (I am familiar with this by now, but a first-time user running into the same bug 5 times in a row and each time NetBeans tells him the bug is fixed, what is she or he going to think ?). 73 exc reports overall. Let's consider it for the next patch(if any). |