The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.
| Tag Class | Total number of occurrences | Tag strings used by tag class |
|---|---|---|
| @todo | 0 | @todo |
| TODO | 9 | TODO |
Each tag is detailed below:
Number of occurrences found in the code: 9
| org.bitrepository.modify.deletefile.ConversationBasedDeleteFileClient | Line |
|---|---|
| Kill any lingering timer threads | 105 |
| org.bitrepository.modify.deletefile.DeleteFileClientComponentTest | Line |
| need more test-cases, e.g. the User-Stories... | 53 |
| org.bitrepository.modify.putfile.ConversationBasedPutFileClient | Line |
| add potential regex from collection settings. | 100 |
| Consider if we can kill possible timer object too, they might be lingering somewhere in the background | 131 |
| org.bitrepository.modify.putfile.PutFileClient | Line |
| handle the cases with validation checksums (pillar-side, client-side and both?). | 36 |
| org.bitrepository.modify.putfile.PutFileClientComponentTest | Line |
| need more test-cases, e.g. the User-Stories... | 54 |
| org.bitrepository.modify.putfile.conversation.SimplePutFileConversation | Line |
| move all the message generations into separate methods, or use the auto-generated constructors, which Mikis has talked about. | 47 |
| org.bitrepository.modify.replacefile.ConversationBasedReplaceFileClient | Line |
| Kill any lingering timer threads | 123 |
| org.bitrepository.modify.replacefile.ReplaceFileClientComponentTest | Line |
| need more test-cases, e.g. the User-Stories... | 61 |
