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 94298 - Create a Java DB/Derby Library when Derby module is there
Summary: Create a Java DB/Derby Library when Derby module is there
Status: NEW
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Libor Fischmeistr
Depends on:
Reported: 2007-02-04 21:47 UTC by vbrabant
Modified: 2013-09-04 08:23 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description vbrabant 2007-02-04 21:47:22 UTC
Once the JavaDB/Derby module is there (means that Java DB/Derby has been
installed) or configured(by example, if you are using JDK 6, Java DB is
delivered with), A Java DB/Derby library should be in the Library Manager, with
all Jars needed therefore.

Same is true for NB5.0, NB5.5, NB5.1

Comment 1 Karthikeyan Rajeswaran 2007-10-26 18:53:45 UTC
In NB6 beta2 library manager, i do see an entry for 'Java DB driver'. Has this issue been fixed? If so, can it be closed?
Comment 2 David Vancouvering 2007-10-26 21:11:13 UTC
yes, I just checked in Beta2 and this appears to be fixed, and marking it so.
Comment 3 Andrei Badea 2007-10-29 11:49:16 UTC
Not fixed. Currently the library is registered by the GlassFish plugin when registering its Java DB instance. But if you
start without a GlassFish bundle on JDK 1.6 (so that the Java DB instance from JDK is registered), there will be no library.
Comment 4 Jiri Rechtacek 2009-10-16 14:13:53 UTC
Reassigned to new owner.