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.
When I select the Diff Settings node in Options, all of the properties have "<Lookup null value>" as their value; when I click any one, an NPE is thrown. The NPE is mine (ObjectEditor...), but something strange is going on with the values. FWIW, IMO this settings node should be deleted anyway - it's a perfect example of settings no user will ever care about, and it's available in the diff UI anyway.
For me it works O.K., but I get the NPE as well. But only for the "Default Diff Service" property. Provided that there is only one diff service anyway, we can remove that property. The other two works O.K. to me. They are useful for setting the default diff engine/visualizer you want to use. It's true that it can be selected in the diff GUI, but if you want to use e.g. an external diff instead of built-in diff always, it's not practical to change it in the diff GUI each time you invoke it. You can also uncheck "Show Diff Service Selector" property of "Built-in Diff Service" in which case you do not get the selector in the diff GUI to save the screen space.
"Default Diff Service" property removed. The other two work O.K. to me. /cvs/diff/src/org/netbeans/modules/diff/DiffSettingsBeanInfo.java,v <-- DiffSettingsBeanInfo.java new revision: 1.10; previous revision: 1.9
*** Issue 45672 has been marked as a duplicate of this issue. ***
> The other two works O.K. to me. They are useful for setting the > default diff engine/visualizer you want to use. It's true that it can > be selected in the diff GUI, but if you want to use e.g. an external > diff instead of built-in diff always, it's not practical to change it > in the diff GUI each time you invoke it. So have the diff system remember the last selected engine/visualizer, and you can still solve the problem and get rid of the setting too.
So, changing the engine/visualizer in the diff GUI will change the defaults. This can be done easily. This behavior can be handy anyway. I've submitted issue #46041 for that.