本文介绍 Eclipse V3.3 中新增的代码清理功能，该功能可以帮助开发者保持代码整洁，提高代码可读性和维护性。文章详细解释了如何配置和使用清理配置文件，并介绍了多种清理选项。
http://www.ibm.com/developerworks/opensource/library/os-eclipse-clean/?S_TACT=105AGX52&S_CMP=cn-a-os（英文）
Keep your code clean with Eclipse V3.3Latest Eclipse offers flexibility in helping you keep your code readable by other developers  |  |
|
Level: Introductory Katrin Limpoeck (limpoeck@de.ibm.com), Software Engineer, IBM 03 Jul 2007 Clean, easy-to-read code allows developers who are unfamiliar with a program to understand it quickly and completely, which makes software maintenance more efficient than the alternative. Get an introduction to the new cleanup capabilities in Eclipse V3.3 that allow developers more options for cleanup than earlier versions. Writing clean code helps other developers read, understand, and maintain the code you write. However, not everyone agrees on the definitions of "pretty, "nice," or "clean." Different developers possess different styles and aesthetic sensibilities. Until now, Eclipse formatted imported code in a simple functional manner with few frills. In Eclipse V3.3, these operations are extended to provide a much broader level of cleanup capabilities. Eclipse V3.3 allows you to clean up code, add missing code, and apply a certain coding style. A wizard helps you configure your cleanup settings and store them for later use. We will discuss the basic concepts of cleanup and give an overview of the tools that help you keep your code squeaky clean. Manage your cleanup configuration with profiles A specific cleanup configuration is called a profile. Profiles can be saved so you can give your settings to somebody else or apply settings from earlier projects and other people to your current code. According to your organization's coding conventions, they can be applied to every Eclipse project, so you get the same code style in all development teams. Eclipse preferences offer management capabilities for profiles. Profiles can be created, edited, and deleted. You can specify the profile used in your workspace globally. When you first open the workspace preferences and navigate to Java > Code Style > Clean Up, you will see the active profile Eclipse [built-in]. This built-in profile is preconfigured and delivered with Eclipse. There are two built-in profiles: Eclipse and Save Participant. These define two minimal cleanup configurations that basically remove unnecessary code. You can see the settings of these built-in profiles by selecting them as the active profile. All details are shown in the details area. Figure 1. Built-in details  Existing profiles can be used as a template of sorts, which can be extended or customized. Therefore, select an existing profile from the drop-down menu as the active profile and click Edit. Built-in profiles can't be changed. Use them as the basis for your own profile or just apply them on your code as-is. To create your own profile, click on New. Name your profile and select an existing profile from the drop-down menu for initialization. Deselect Open the edit dialog now and click OK. Figure 2. New profile  To share your profile, use the export functionality. To open the profile, click Edit, then Export. Name your profile file, click OK, and it is ready to share. Figure 3. Exporting profiles  To apply an external profile from an XML file to your project, you must import it first. Click Import in the main cleanup preferences, select the file, and click OK.
Cleanup settings are divided into five main categories. Each appears in its own tab, which consists of the settings section and the preview section. Preview shows how the settings affect the code immediately. Play around with the settings and watch how the code in the preview changes to get an idea of how each change affects your code. The dialog to edit all these settings pops up after you click Edit in the main cleanup preferences or when you create a new profile and select Open the edit dialog now. The following discusses what settings are possible, along with their pros and cons. Since many settings are matter of taste, we will not offer recommendations. Note that when you do not select a specific option, your code will remain as you typed it. The first tab deals with coding styles and defines how blocks, expressions, and variable declarations should appear.
Figure 4. Coding styles  The second tab lets you define how members of your types should be accessed.
Figure 5. Member Access  The third tab allows you to specify settings for removal of unused and unnecessary code.
Figure 6. Unnecessary code  The fourth tab allows you to add missing code.
Figure 7. Missing Code  Last but not least, the fifth tab helps you organize your code.
Figure 8. Code organizing 
Once a cleanup profile is created, there are different ways of applying it to your code. The easiest way is to open the context menu in the Java Editor and select Source > Clean Up. Figure 9. Open the cleanup wizard  This will bring up the cleanup wizard, shown below. Figure 10. Cleanup wizard  The wizard guides you through the cleanup of the selected sources. The description in the upper left shows how many projects and compilation units will be cleaned up. Usually, you would apply the configured profile to your compilation units. However, it is possible to customize the code clean just before applying it. This may be helpful if you want to check how a certain setting affects the result in your code. The cleanup wizard can be launched on any Java project, package, or Java file if at least one compilation unit is contained. For example, you can select all your Java projects in the workspace and launch the wizard. Performing the cleanup would affect all compilation units in your workspace that can be refactored with the selected profile. By default, there is one global cleanup profile for the whole workspace. However, it is possible to enable project-specific cleanup in your project properties. Each project can have its own cleanup profile. To enable this, simply open the project properties and navigate to Java Code Style > Clean Up, as shown below. Figure 11. Applying profiles  To preview the result of the cleanup, click Next in the cleanup wizard. The wizard now computes the changes to your code. Depending on the amount of compilation units selected, this might take a while. On the next page, you will be presented with the changes that will be applied. Figure 12. Previewing results  The tree lists all compilation units that will be affected by the cleanup. You can step into the tree to select different changes of a compilation unit. Selecting a change shows the original source and the refactored source in a compare view. After reviewing the changes, you might not want all of them to be applied. In this case, you can simply uncheck the changes that should not be executed. Clicking Finish will perform the whole cleanup action.
Some of the cleanup refactoring actions like Convert for loops to enhanced or Add missing annotations are bound to Java code compliance 5.0 or 6.0 and can only be applied if the source file is compiled according to the required Java version. The cleanup wizard allows you to select those refactoring options no matter what Java version is used. So if you wonder why your Once you have run the cleanup wizard a few times and your profile is set up correctly, you might not want to click through the wizard every time you clean up. In this case, you can simply disable the wizard in the profiles settings page under Preferences > Java > Code Style > Clean Up. Figure 13. Hide/show cleanup wizard  Performing code cleanup on many resources often results in many changes. The wizard allows you to preview those before applying them. However, having hundreds of files affected makes reviewing uncomfortable, especially when you are looking for a certain change in the review. Use the filter option to narrow the list of changes shown in the preview page. Usually, almost every file is affected by a source code formatting action, but not many are affected by the action that adds a missing deprecation annotation. In this case, the filter helps you find those files by filtering out other changes. The filter is in the upper-right corner of the preview page. Figure 14. Applying filters  Cleanup actions can not only be performed by hand but also during the save action of a Java file. To enable this feature, go to Window > Preferences > Java > Editor > Save Actions and select additional actions. Configure the cleanup actions as described above, and they will be performed on every save of a Java file. Please note that those actions can be expensive and slow down your workbench. Also, you might get confused that the code you just wrote looks different after the save if you don't have the cleanup in mind anymore. Figure 15. Performing cleanup on save 
Cleanup is a helpful tool that makes your code look better and helps others find their way through it. It might even make your code more robust. However, coding style is a matter of taste. For example, people who avoided too many quotes in the past won't use blocks wherever possible now just because the cleanup wizard offers that action. Cleanup does not fix conceptual or functional problems — at least not with the current version of Eclipse. But it can save a lot of work by presenting code in a clear manner. The actions that come with the wizard are rich, and cover many points in coding styles and conventions. Organizations must decide on their own style and convention, and, therefore, it would be helpful to have the wizard being extensible, which is not the case in Eclipse V3.3. The cleanup concept not only make sense in the Java world but also could be useful for other languages like C/C++, PHP, Python, Perl, etc. It will be interesting to see how this feature is adopted by the community and the directions it will evolve. Learn
Get products and technologies
Discuss
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
