Community
Participate
Working Groups
Build ID: I20081030-1917 Steps To Reproduce: My expectation that sort members would sort the members based on the definitions in Java/Appearance/Member sort order but instead it just sort the variables alphabetically (which is not desirable in my case but would be nice to have it as a separate option). More information: I am not sure what triggers Java/Appearance/Member sort but exected it to be triggered by cleanup/save actions and to deal with code ordering cleanup (such as imports order) and not alphabetical sort order.
BTW, I created this one and https://bugs.eclipse.org/bugs/show_bug.cgi?id=257149 after creating https://bugs.eclipse.org/bugs/show_bug.cgi?id=256717 and being asked to split the Jira issues. Also, this one clarify that the bug is not necessary related to the formatter (thought in my case I would like to trigger them together via cleanup task or save actions).
Works for me using I200812021812 (both, clean up and save action). If you still see this using said build then please provide a step by step test case and reopen this bug.
I am using the latest 3.5M4 and still though it applies now the structure changes based on the settings defined in "Member sort order" it also sort alphabetically. For me it is undesirable and there is no settings to enable or disable it. As it looks the "Member sort order" is about code structuring based on java element type (inner class, member, statics, function,..) and also optionally based on visibility but no where does it mention alphabetical order. To reproduce it write two methods (bbb and aaa) and when apply cleanup or save action you should see aaa being moved to be above bbb.
OK, so this has nothing to do with clean up or save actions - it's just how we currently do member sorting. *** This bug has been marked as a duplicate of bug 142899 ***
