17 Sep
2012
17 Sep
'12
8:38 a.m.
Status: New
Owner: ----
CC: anquetil...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 838 by tudor.gi...(a)gmail.com: 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
17 Sep
17 Sep
9:29 a.m.
New subject: Issue 838 in moose-technology: VerveineJ does not export non-javadoc comments
Updates:
Status: Accepted
Comment #1 on issue 838 by anquetil...(a)gmail.com: 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.
1 Feb
1 Feb
7:50 p.m.
New subject: Issue 838 in moose-technology: VerveineJ does not export non-javadoc comments
Updates:
Status: Started
Comment #2 on issue 838 by anquetil...(a)gmail.com: 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
4342
days inactive
4479
days old
2 comments
1 participants
participants (1)
-
moose-technology＠googlecode.com