Details
-
Type:
Bug
-
Status:
Open
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Number of attachments :
Description
If a class has an identifier, say a field, that uses characters other than the ones specified below, the parsing stops there and the rest of the fields will not be included into the DocInfo object. Therefor any todos for those fields will not be included.
The root of this problem is not in the tasklist-plugin itself, but it affects the reports made by it. I have done some digging and found this in the QDox source code:
[A-Za-z_$0-9]*
{ return Parser.IDENTIFIER; }Somewhere inside either QDox och vdoclet (@sourceforge) there should be a loop that goes through all the fields in a class. The parser will probably throw a ParseException when it discovers a "bad" field. Now if that exception was caught inside the loop instead of outside the loop, we should at least be able to parse the rest of the fields.
Because of MPTASKLIST-10 I have not been able to verify if this affects methods as well, but my guess is that it does.
Since this is out of scope for this plugin I suggest that we add some user-documentation for this. Just to let them know about this limitation. Perhaps a "Known limitations" section in xdocs/index.xml. I can put together something later on, if you like.
Issue Links
- is duplicated by
-
MPTASKLIST-10
Method todos are never found even if they exist in the code
-
This is a Java class that can be used to test this issue. When I include this class in a Maven tasklist report I get the following results:
Class Class Todos Method Todos Fields Todos
PersonBean 1 0 1
but the results should be these:
Class Class Todos Method Todos Fields Todos
PersonBean 1 6 3
Ignore the "Method Todos" column here, it has it's own issue
MPTASKLIST-10.