1) Create suite1 and suite2
2) Create a module in a suite1
3) Add the module (created in step 2) to suite2
Attached exception is thrown.
Cf. http://www.netbeans.org/nonav/issues/show_bug.cgi?id=79209 (CCing Radim)
Created attachment 32122 [details]
assertion due to missing CTL_MainWindow_Title_No_Project
$ nbcvs -q ci -m "#80919: moving main window title keys changed as part of
#79209 fix back because API support relies on them" core/windows
Checking in core/windows/src/org/netbeans/core/windows/view/ui/Bundle.properties;
new revision: 1.16; previous revision: 1.15
initial revision: 1.1
<-- Bundle.propertiesnew revision: 1.78; previous revision: 1.77
Checking in projects/projectui/src/org/netbeans/modules/project/ui/Hacks.java;
new revision: 1.23; previous revision: 1.22
new revision: 1.7; previous revision: 1.6
This should be OK now. I added test into core/windows with comment that these
keys are used in API support
IMHO the original change was correct and apisupport just needed to be updated to
use the new bundle keys. No?
In fact keys in core/windows are API now so it seems to be easier to access them
from projects/projectui if neceseary. At least we do not have to pay attention
what version of platform we are developing against and introduce some logic of
this kind into API support.
Probably we should document these keys into arch of core/windows (has to be
created) or openide/windows.
The trouble with the original keys is that they are inappropriate for platform
developers. You want just one thing to brand; the "project" makes no sense. That
is why I welcomed the simplification. Of course some kind of switch in
apisupport would be necessary to support both old and new styles.
Oh well, probably not worth bothering with further.