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 40870 - Exception on startup, using Java 1.5 beta
Summary: Exception on startup, using Java 1.5 beta
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: Other Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-09 15:46 UTC by mzimmerm
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Exception text (1.15 KB, text/plain)
2004-03-09 15:48 UTC, mzimmerm 		Details
The ide.log at time of exception (275.55 KB, text/plain)
2004-03-09 15:49 UTC, mzimmerm 		Details
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 mzimmerm 2004-03-09 15:46:19 UTC 
There is an exception any time  Netbeans start. I am 
using 1.5 beta. If I remember, the exception only 
happens after I updated the modules.
Comment 1 mzimmerm 2004-03-09 15:48:10 UTC 
Created attachment 13905 [details]
Exception text
Comment 2 mzimmerm 2004-03-09 15:49:26 UTC 
Created attachment 13906 [details]
The ide.log at time of exception
Comment 3 Milan Kubec 2004-03-09 21:30:07 UTC 
Did you use autoupdate multiple times for the same module? Or what
have you done before the exception shown up.
Comment 4 pfelenda 2004-03-14 21:25:08 UTC 
Please provide the names of modules you updated.
If you know steps to reproduce the exception provide it too.
Thanks
Comment 5 pfelenda 2004-06-16 15:00:20 UTC 
Without detailed steps to reproduce, we can't fix this issue.
Comment 6 Ondrej Rypacek 2004-06-16 15:09:37 UTC 
Although not well specified, this is certainly not a bug of tasklist.
It is related to updating as the first comment describes.
Comment 7 Jiri Rechtacek 2004-06-29 10:26:12 UTC 
Ondro, I don't think is may be a Autopdate problem, the root of
problem in java/Util. But the code of java module has been a lot
changed (big merge of Refactoring) we are not able to track the
problem because o lack of information in issue's description. It's
closed as worksforme.