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.
Please provide some kind of document (can be brief), which clarifies what refactoring functionality is provided in apisupport. Some functionality is provided, some not, but definitly hard to guess what is expected to work and what not. Thx.
Created attachment 29832 [details] html document describing refactorings.
here is the doc. it describes the situation as of 5.0 (also current trunk) given that the layer refactorings are not quite there it would be probably better to remove them. Which also means removing the layer where-user. opinions?
You mean that you would remove "Safe delete" and "Find Usages" capabilities at all for layer.xml? Please don't do that I really like both and I think they are both quite useful (even with that harmless(?) bug leaving a shadow there). And also it will safe (or ease) a some mailing list traffic "How can I delete my action?" ;) I would vote for just putting the attached document somewhere. As a starting point wiki would be enough IMHO.
> Which also means removing the layer where-user. Umm, I do not understand the above sentence...
the sentence should read "Which also means removing the where-used query for layer files." Basically having a where used and some refactorings partly written lets the user assume the rest works as well, which is not true and I have a few bugs regarding that and I unfortunately don't plan to fix them. The layer usecases are way too complex for a bulletproof undo for example. Additionaly it doens't matter for meta-inf/services and manifest entries to be limited to one module only, but with layers and their orderings, this design simplification that I imposed on the refactorings, starts to leak out.. it is my fault that it even got there. The layer refactorings are not ready for prime-time imho.