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.
I think there is no longer any need to recommend to users that new JDBC drivers be put on the classpath - at least, not in NB 3.4, I am not sure about 3.3. Try putting drivers in modules/patches/org-netbeans-modules/db/ You can put a README.txt in that dir in db/release/ to make it easier for users (cf. ant module). This will put the drivers in the module classloader for the DB module. In NB 3.4, acc. to issue #20663, this will also make them available in the context classloader for all threads. That may be enough to have the drivers be used anywhere in the system, without affecting the classpath. Also in the FAQ is says you can use $CLASSPATH instead of lib/ext/. This is not true, I think; $CLASSPATH is ignored by the launcher.
Set target milestone to TBD
The driver registration will be changed. It wil be possible to register a JDBC driver on the fly, without restarting the IDE, and it will be not necessary to put the driver file into lib/ext directory.
Good news!
Martin, FYI.
*** Issue 34576 has been marked as a duplicate of this issue. ***
UI specification http://db.netbeans.org/uispecs/db_jdbc_driver_manager.html
I guess this should be at least P2 as it blocks P2. Also there is no target milestone set.
Yes, need at least promo-D target milestone.
New registration of the JDBC drivers was implemented. For more info see: http://db.netbeans.org/doc/jdbc_registration.html http://db.netbeans.org/uispecs/db_jdbc_driver_manager.html
OK