Eclipse tasks instructions

Tasks can add identifiers in the Code and quickly locate the identifiers through tasks view, which helps improve development efficiency and code management.

You can open the task management view through eclipse window =, show view =, and tasks.

Let's take a look at the example (check the check box on the left of the line number ):

The methods in the figure are described as follows:

F0 is a common method

F1, F2, and F3 are the default task identification methods added to the annotations,

F4 is the method for adding task identifiers through eclipse

F5 is the method for adding a custom ID

(Note that the task id can be added to any location, not just the method)

Where

Xxx generally indicates that the function has been implemented, but is to be optimized.

Todo indicates that a function needs to be implemented here.

Fixme generally refers to a logical error or exception.

F1, F2, F3, and F4 are two different ways to add tasks.

Tasktype makes it easy to see the differences. One is javatask and the other is task.

The identifier of the F1, F2, and F3 methods is implemented by adding the keyword XXX, todo, or fixme to the code comment. Task view cannot be edited.

The F4 method adds a task id by right-clicking on the left of the row number and selecting add task. You can edit and manage the task view.

It is worth mentioning that, although the F4 method task identifier can be managed through the task view, this identifier is also easy to lose. For example, you cut and paste the F4. You will find that the task identifier is lost, or even you delete the F4 method, and then the CTRL + z identifier will still be lost. Because this identifier depends on Eclipse, while F1, F2, and F3 are dependent on code. We recommend that you use the task Identification Method of F1, F2, and F3.

The F5 method is user-defined. You can search for task = in Windows =, preferences =, and find the task tags in Java to add.

By default, eclipse adds statements such as // todo auto-generated method stub to automatically generated methods. If many of these automatically added identifiers do not affect our tasks. Therefore, we recommend that you remove this sentence from the code template. For Windows =, search for code templates =, and find code =, method body =, under Code templates in Java. Edit the code, remove // $ {todo} auto-generated method stub.

Some people ask/$ todo auto-generated method stub if it can be deleted in batches. I can only regret to say no, because this identifier comes from the code. You can use the tasks view to find one of these identifiers and delete them one by one.