[ http://jira.codehaus.org/browse/MPTASKLIST-11?page=all ]

Jason van Zyl updated MPTASKLIST-11:
------------------------------------

    Assign To:     (was: Jason van Zyl)

> Non-US-ASCII characters in identifiers hinders todos from being included
> ------------------------------------------------------------------------
>
>          Key: MPTASKLIST-11
>          URL: http://jira.codehaus.org/browse/MPTASKLIST-11
>      Project: maven-tasklist-plugin
>         Type: Bug

>     Reporter: Dennis Lundberg
>  Attachments: PersonBean.java
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to