| Summary: | Refactor -> Rename Foo.java forgets to update item 'Name' in Application Descriptor | ||
|---|---|---|---|
| Product: | [Tools] MTJ | Reporter: | Markus Salamon <bugs.eclipse.org> |
| Component: | MTJ projects | Assignee: | Project Inbox <dsdp.mtj-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | ||
| Version: | 1.1 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Markus Salamon
What does 'Name' refer to is it the me MIDlet-Name: attribute or the name of a midlet on Midlet-n attribute That would be the name of a MIDlet on the MIDlet-n attribute. After renaming FooTest.java to BarTest.java the result resembles: MIDlet-1: FooTest,,de.illogic.test.BarTest It's already faulty when you preview the renaming changes. A default value for a midlet name is created out of the class name only. After the creation MTJ assumes that the midlet name is determined by the developer and does not attempt to change it. This is more like an enhancement request for MTJ to keep controlling the midlet name until the default value is changed. I agree when a project has only one MIDlet. Still when I check "Update all textual occurrences in comments and strings" during the rename operation, this is simply not the behavior I'd expect. Especially when working on a MIDlet suite with several MIDlets in it. |