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 27965 - __USER__ attribute in Java Class/Main file create Wizard sometimes instantiated incorrectly
Summary: __USER__ attribute in Java Class/Main file create Wizard sometimes instantiat...
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-11 22:04 UTC by Bryan T. Vold
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan T. Vold 2002-10-11 22:04:48 UTC 
Sometimes when using the "New file" wizard, choosing 
<Right-click on Explorer>/New/Java Classes/Main - the 
__USER__ attribute in the template sometimes instantiates 
with my login (a 4-digit number) instead of the USER 
string I have defined in Options/Java Sources/Strings 
Table (Bryan T. Vold).  Most of the time the attribute 
instantiates correctly, but it this bug happens frequently 
enough that it is annoying.  Also, as a side note, I am 
creating this file (I have been 
creating "HelloWorld.java") under a CVS-controlled 
directory.  I have messed around Add'ing the file into 
CVS, removing it and deleting it.  I haven't figured out a 
way to reproduce it every time.
Comment 1 Jesse Glick 2002-10-11 22:26:47 UTC 
You got the wrong module.
Comment 2 Svata Dedic 2003-01-09 18:24:29 UTC 
Sadly I can not reproduce the bug at all. If you find any
circumstances leading to the error, please reopen the issue and post
the reproduction steps.
I have tried to create files from various templates both right after
IDE install and during normal work, but everything seems to be OK.
Please check whether the String Table property in Tools | Options |
Editing | Java Sources contains the proper value -- the bug may be
caused by improper (de)serialization of the stringtable.