Issue 838 in moose-technology: VerveineJ does not export non-javadoc comments

Status: New
Owner: ----
CC: [hidden email]
Labels: Type-Defect Priority-Medium Component-VerveineJ

New issue 838 by [hidden email]: VerveineJ does not export  
non-javadoc comments
http://code.google.com/p/moose-technology/issues/detail?id=838

VerveineJ exports javadoc comments for both types and methods.

However, it does not export line comments like:
//This is also a relevant comment

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Status: Accepted

Comment #1 on issue 838 by [hidden email]: VerveineJ does not export  
non-javadoc comments
http://code.google.com/p/moose-technology/issues/detail?id=838

It has been bugging me too, but the Parser we use (JDT), only keeps javadoc.
I did not find how to tell it to keep also other comments.

Another solution would be to read again the source files to get that info.
But it would be slow.


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Status: Started

Comment #2 on issue 838 by [hidden email]: VerveineJ does not export  
non-javadoc comments
http://code.google.com/p/moose-technology/issues/detail?id=838

looked at it a bit
It turns out some of the non-javadoc comments are associated with entities  
by JDT ("leading comments")
I created these ones.

Other comments (e.g. at the very beginning of a class file) should be  
treated.
But it can be a bit tricky to link them to the right Famix entity

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev