Community
Participate
Working Groups
Build Identifier: 20110916-0149 the start/stop/modify method names as well as bind/unbind ones are not considered while refactoring a method name. Also refactoring the classname does not change the corresponding one in the implementation element. The last case can be worked around with using the "search in other files for qualified name" function but this requires a whole scan of all files and manual review. Reproducible: Always Steps to Reproduce: 1. Create Component 2. Refactor Name/Method
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
This is still an issue AFAIK. What I currently do is activate the text-search on refactorings, but as for example in plugin.xml it is also detected without that option there must be a way to accomplish this already.
This issue is about handwritten component xmls right? If you're using the DS builder, any refactoring should be reflected.
Handwritten or edited by the component editor doesn't really matter. I know I can use annotation based XML generation and this would work, but also here it requires that the plugin is activated all the time and not all setup allows annotation based components.
