You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/07/24 00:43:10 UTC
[jira] Created: (MPTASKLIST-11) Non-US-ASCII characters in identifiers hinders todos from being included
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPTASKLIST-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPTASKLIST-11
Summary: Non-US-ASCII characters in identifiers hinders todos from being included
Type: Bug
Status: Open
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-tasklist-plugin
Assignee: Jason van Zyl
Reporter: Dennis Lundberg
Created: Fri, 23 Jul 2004 6:42 PM
Updated: Fri, 23 Jul 2004 6:42 PM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPTASKLIST-11) Non-US-ASCII characters in identifiers hinders todos from being included
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Dennis Lundberg
Created: Thu, 4 Nov 2004 5:53 PM
Body:
I have tried the new version of qdox and it solves the problems that this issue descibes. So here a shortlist what needs to be done (IMHO) to resolve and close this issue:
1. Await the final release of qdox 1.6
2. Get qdox-1.6 up on ibiblio
3. Persuade Mike to make a new timestamped build of vdoclet
4. Get that up on ibiblio
5. Patch the project.xml for the maven-vdoclet-plugin to use the new versions
6. Release maven-vdoclet-plugin-1.3
7. Release tasklist-plugin-2.4
Have I missed something?
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPTASKLIST-11?page=comments#action_26080
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPTASKLIST-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPTASKLIST-11
Summary: Non-US-ASCII characters in identifiers hinders todos from being included
Type: Bug
Status: Open
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-tasklist-plugin
Assignee: Jason van Zyl
Reporter: Dennis Lundberg
Created: Fri, 23 Jul 2004 6:42 PM
Updated: Thu, 4 Nov 2004 5:53 PM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPTASKLIST-11) Non-US-ASCII characters in identifiers hinders todos from being included
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Dennis Lundberg
Created: Fri, 23 Jul 2004 7:53 PM
Body:
Raised this issue with the developers of vdoclet
http://sourceforge.net/tracker/index.php?func=detail&aid=996903&group_id=47842&atid=451063
and QDox
http://jira.codehaus.org/browse/QDOX-61
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPTASKLIST-11?page=comments#action_22233
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPTASKLIST-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPTASKLIST-11
Summary: Non-US-ASCII characters in identifiers hinders todos from being included
Type: Bug
Status: Open
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-tasklist-plugin
Assignee: Jason van Zyl
Reporter: Dennis Lundberg
Created: Fri, 23 Jul 2004 6:42 PM
Updated: Fri, 23 Jul 2004 7:53 PM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPTASKLIST-11) Non-US-ASCII characters in identifiers hinders todos from being included
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Fri, 23 Jul 2004 7:28 PM
Body:
Could you also report the issues to the projects this plugin rely on?
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPTASKLIST-11?page=comments#action_22232
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPTASKLIST-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPTASKLIST-11
Summary: Non-US-ASCII characters in identifiers hinders todos from being included
Type: Bug
Status: Open
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-tasklist-plugin
Assignee: Jason van Zyl
Reporter: Dennis Lundberg
Created: Fri, 23 Jul 2004 6:42 PM
Updated: Fri, 23 Jul 2004 7:28 PM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPTASKLIST-11) Non-US-ASCII characters in identifiers hinders todos from being included
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Dennis Lundberg (mailto:dennis.lundberg@mdh.se)
Date: Fri, 23 Jul 2004 7:09 PM
Comment:
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.
Changes:
Attachment changed to PersonBean.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MPTASKLIST-11?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPTASKLIST-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPTASKLIST-11
Summary: Non-US-ASCII characters in identifiers hinders todos from being included
Type: Bug
Status: Open
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-tasklist-plugin
Assignee: Jason van Zyl
Reporter: Dennis Lundberg
Created: Fri, 23 Jul 2004 6:42 PM
Updated: Fri, 23 Jul 2004 7:09 PM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPTASKLIST-11) Non-US-ASCII characters in identifiers hinders todos from being included
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Mike Williams
Created: Tue, 2 Nov 2004 7:01 AM
Body:
The underlying bug in QDox (QDOX-61) has now been fixed (in qdox-1.6-SNAPSHOT).
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPTASKLIST-11?page=comments#action_25999
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPTASKLIST-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPTASKLIST-11
Summary: Non-US-ASCII characters in identifiers hinders todos from being included
Type: Bug
Status: Open
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-tasklist-plugin
Assignee: Jason van Zyl
Reporter: Dennis Lundberg
Created: Fri, 23 Jul 2004 6:42 PM
Updated: Tue, 2 Nov 2004 7:01 AM
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org