Created attachment 97110 [details]
My local build 100412-db5178d59a01 from today.
1) created a new Maven NetBeans Application project set, including an empty module
2) added an Action to the module
3) built the NetBeans Platform Application project using Build action
4) ran the NetBeans Platform based Application project using Run action
The action added in step 2 is present in the UI, but has an empty name in the app's main menu. The console shows an exception (see the attachment here).
CTL_SomeAction key was added by the Action wizard in Bundle.properties of the module.
The behavior seems somewhat random. I tried reproducing several times and only once I was able to see the problem again and rebuild of the application fixed it. I did not find out why.
I can reproduce, but I'm looking at it with disbelief :-) as Bundle.properties and layer.xml are correctly generated IMHO. There must be smt hidden...
Jaro, can you help us find reproducible steps for this issue?
I don't think we need new reproducible steps,since I'm able to reproduce issue with steps you have provided. My prerequisites contains also clean userdir and deleted .m3 directory, though.
I meant .m2 directory, of course ;-)
I found a case when I am able to reproduce the problem consistently.
When I do a change to a module (e.g. mavenapplicationtest-module1) and rebuild only that module (action Build on mavenapplicationtest-module1), then subsequent Run of the Platform based Application project manifests this bug.
After I rebuild with dependencies the Platform base Application project, next Run is OK.
My observations are that the bug is really random and perhaps building of binaryFS cache may be at fault. The bug disappears whenever Bundle file is modified and module is rebuilt and in case of non-empty real world actions, this bug is not reproducible at all.
Lowering to P3 and marking as random.
Note that artifacts/jars created seems to be OK, as bug can be reproduced randomly with the same set of jars, just by running created App from command line.
I tried to debug into BinaryFS, but without success. However it seems that for some reason Bundle.properties is not parsed well - most probability of bug occurrence seems to be when bundle key is on the very first place of Bundle.properties.
apisupport's usage of BinaryFS is does not count as a filesystems error. I am not sure if it is more module system or independent problem. I can just note that I've already suggested the apisupport to copy BinaryFS and modify it according to their needs.
I don't understand comment #9 at all; comment #8 indicates that this is not an apisupport issue, so it is either a bug in BinaryFS or in module resource caches - right?
Reassigning to maven