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 23024 - Sun JDK 1.4 - computeSerialVersionUID not found
Summary: Sun JDK 1.4 - computeSerialVersionUID not found
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: serialversion (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: Jaroslav Tulach
URL:
Keywords: JDK_SPECIFIC
Depends on:
Blocks:
 
Reported: 2002-05-02 00:10 UTC by Fred McLain
Modified: 2011-06-09 09:51 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 Fred McLain 2002-05-02 00:10:21 UTC
I'm not the first to see this, search nbusers for 
computeSerialVersionUID.

Repro: Using JDK 1.4 right 
click on a serializable source file and select 
"Tools/Check Serial UID".   A stack trace appears in the 
Serial UID Console:

Checking class 
xyz
java.lang.NoSuchMethodException: 
computeSerialVersionUID
        at 
java.lang.Class.getMethod0(Class.java:1742)
        at 
java.lang.Class.getDeclaredMethod(Class.java:1219)
 
       at 
org.netbeans.modules.serialversion.SVUIDAction.checkClassElement(SVUIDAction.java:296)
 
       at 
org.netbeans.modules.serialversion.SVUIDAction.access$0(SVUIDAction.java:249)
 
       at 
org.netbeans.modules.serialversion.SVUIDAction$1.run(SVUIDAction.java:118)
 
       at org.openide.util.Task.run(Task.java:152)
        at 
org.openide.util.RequestProcessor$ProcessorThread.run(RequestProcessor.java:622)
Scanning 
finished
Comment 1 Jesse Glick 2002-05-02 04:34:05 UTC
I don't know if anyone is actively working on this module, as it is
considered experimental - if you care enough about the bug you may
consider finding a patch yourself, I doubt it would be too difficult.
Comment 2 Marek Grummich 2002-07-22 11:33:09 UTC
Set target milestone to TBD
Comment 3 Jaroslav Tulach 2003-01-31 16:21:00 UTC
I have just found this issue. I'll try to do something with it.
Comment 4 Jaroslav Tulach 2003-04-18 13:16:18 UTC
The code has been rewritten, this is obsoleted issue.
Comment 5 gugrim 2003-05-01 10:39:38 UTC
What does it mean, "the code has been rewritten"? Is there a working
version somewhere? 
Comment 6 Jaroslav Tulach 2003-05-02 09:12:58 UTC
Of course. In CVS or in AutoUpdate.
Comment 7 zacjacobson 2003-05-02 18:00:40 UTC
When can the average user (such as myself) expect a release of this fix?

I still see this same issue in NetBeans 3.4.1. The module that is
actually available from the Update Centres and from the website is
0.2_dev-16.

If I have a serialVersionUID in the class already, and run the tool,
the stack trace is printed out. Then the dialog will come up, and
correctly report the Current SVUID, but say that the New SVUID is N/A.

My stack trace is slightly different that what's reported below:

Checking class com.xyz.whatever.SomeClass
java.lang.NoSuchMethodException:
java.io.ObjectStreamClass.computeSerialVersionUID(java.lang.Class)
        at java.lang.Class.getMethod0(Class.java:1756)
        at java.lang.Class.getDeclaredMethod(Class.java:1233)
        at
org.netbeans.modules.serialversion.SVUIDAction.checkClassElement(SVUIDAction.java:296)
        at
org.netbeans.modules.serialversion.SVUIDAction.checkDataObjects(SVUIDAction.java:237)
        at
org.netbeans.modules.serialversion.SVUIDAction.access$1(SVUIDAction.java:220)
        at
org.netbeans.modules.serialversion.SVUIDAction$1.run(SVUIDAction.java:127)
        at org.openide.util.Task.run(Task.java:136)
        at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:599)
Scanning finished
Comment 8 Jesse Glick 2003-05-02 18:14:00 UTC
zacjacobson - Definitely not in NB 3.4. This is an unsupported module,
remember; fixes are not generally backported to old IDE versions.
Current sources to the module are available in CVS, but there are no
resources to make official binary releases. The Alpha update center
gets an (untested) nightly build of the module from sources.

NB 3.5's AU has serialversion 0.5.1; not sure if that contains the
fix. The dev AU is supposed to have 1.1 (though dev alpha AU is
completely broken at the moment, reported separately). Yarda please
set Target Milestone to 3.5 or 4.0; it cannot be TBD if the issue is
closed. Also mark FIXED, not WORKSFORME, if there was really a problem
before and it is now fixed.
Comment 9 Jaroslav Tulach 2003-05-05 08:31:37 UTC
As this module does not have target milestone 3.5, I am setting it to
4.0, but right now I checked that if I use AutoUpdate Center Beta in
3.5RC1 I can see Serial Version UID version 1.1. 

As concern 3.4 - somebody would have to backport the module (pretty
easy I guess), but I have no interest in doing that, as I am using
main trunk builds.
Comment 10 Jesse Glick 2003-05-05 15:24:27 UTC
I added 3.5 as a version and target milestone.
Comment 11 Marian Mirilovic 2011-06-09 09:51:06 UTC
v/c