This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 13758 - AutoComment place my commets inside variable definition
Summary: AutoComment place my commets inside variable definition
Status: CLOSED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-19 16:49 UTC by dmladek
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dmladek 2001-07-19 16:49:03 UTC
[NBdev-200107190100]
jdk1.3.1, rh70
=====================

I defined some varibles in my class, eg:

    static boolean verbose = true;
    final static String IDE_HOME = ....;
    static String doc_items[];

I used auto comment tool to commet my class including those
variables.
After thet I was surprised because comments was placed after word static
and it looks like:

    static 
    /** setting it to true makes that this program will print debug messages
     *
     * usefull to use it as a parametr "-v" from command line.
     */
    boolean verbose = true;
     /** this is the $IDE_HOME variable
     */
    final static String IDE_HOME =....;


Seems that autocommet tool has problems when definition starts with the world:
"static".
Comment 1 Petr Suchomel 2001-07-20 08:20:41 UTC
Commnets are handled by java module
Comment 2 dmladek 2001-07-20 09:04:42 UTC
hmmm....I thourht it, but I spoke with someone and he advice me javadoc module:-) Sorry about that.
Comment 3 Svata Dedic 2001-07-20 09:18:07 UTC
I think I need to clarify the assignment (I am the one Dan has spoken to):
Javadoc module is responsible for UI of the java doc editing and
manipulation tools. Java module is responsible for storing to and
retrieving javadoc from java sources. The distinction where one
module's work end and another's one start is very unclear (the same
with javabeans vs. java).
Comment 4 Svata Dedic 2001-08-30 17:20:48 UTC
I cannot reproduce it with dev-30/08/2001.
If you spot the bug again and it is reproducible, please attach the 
exact source file (or send it to me to my e-mail addr).
Comment 5 dmladek 2001-08-30 17:54:06 UTC
I don't believe that it somehow disappears, probably more it was
somehow fixed:-) AND NOW it works good:-) in [NBdev-200108300704]
Comment 6 Quality Engineering 2003-07-01 13:15:00 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.