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.
When the IDE is running on Java 6, we should use the JavaDB database bundled with Java 6 and make it available to NetBeans users, in the following ways: - add the Derby/JavaDB drivers to the Databases node in the Runtime tab - add the Derby/JavaDB drivers to the Library Manager (so Derby they can be easily used in Java SE applications) - install the sample Derby database that we bundle in the IDE and register the corresponding connection in the Databases node in the Runtime tab
As of November 20 the Java DB instance bundled with JDK 6 is detected and the drivers are registered in the Runtime tab. Adding the drivers to the Library Manager is a larger issue, as it doesn't only apply to Derby, but to all databases.
Also registering the sample database when a Java DB instance was detected. Checking in src/org/netbeans/modules/derby/Bundle.properties; /cvs/db/derby/src/org/netbeans/modules/derby/Bundle.properties,v <-- Bundle.properties new revision: 1.18; previous revision: 1.17 done Checking in src/org/netbeans/modules/derby/Installer.java; /cvs/db/derby/src/org/netbeans/modules/derby/Installer.java,v <-- Installer.java new revision: 1.2; previous revision: 1.1 done Checking in src/org/netbeans/modules/derby/api/DerbyDatabases.java; /cvs/db/derby/src/org/netbeans/modules/derby/api/DerbyDatabases.java,v <-- DerbyDatabases.java new revision: 1.3; previous revision: 1.2 done
I just saw that JDK 6 also contains a sample database toursdb under: db/demo/databases See also: http://wiki.netbeans.org/wiki/view/JavaDBMustang It would be useful to automatically register this database as well.
The bundled Java DB will be installed in various locations in JDK 6 update 2: 1. /opt/SUNWjavadb on Solaris package (SVR4) based installs 2. /opt/sun/javadb on Linux package (RPM) based installs 3. C:\Program Files\Sun\JavaDB (or the local equivalent) on Windows 4. $JDK_HOME/db for file based installs (same as today) Will need to check all these locations (currently only #4 is checked).
Note that whenever Apple ships a corresponding version of the JDK (Java SE 6 is still in Developer Preview), they may install JavaDB in yet another location.
This is important to do, it goes against user expectations. It should be registered automatically
*** Issue 101433 has been marked as a duplicate of this issue. ***
Still leaving open, need to test on Windows. Checking in src/org/netbeans/modules/derby/JDKDerbyHelper.java; /cvs/db/derby/src/org/netbeans/modules/derby/JDKDerbyHelper.java,v <-- JDKDerbyHelper.java new revision: 1.3; previous revision: 1.2 done
Using System.getenv() to get an environment propery instead of System.getProperty("Env-FOO"). With this change Java DB is detected correctly on Windows. Checking in src/org/netbeans/modules/derby/JDKDerbyHelper.java; /cvs/db/derby/src/org/netbeans/modules/derby/JDKDerbyHelper.java,v <-- JDKDerbyHelper.java new revision: 1.4; previous revision: 1.3 done
Still waiting for the final decision on the location of Java DB in the file-based JDK distributions, so downgrading to P3 and leaving open.
I believe the fix mentioned in desc10 is not quite correct. We should assign Java DB settings to use the Java DB installed by Java 6 only if the IDE is using Java 6. My opinion is we should only use settings "known" by the IDE.
You are right, will fix for 6.0.
Fixed the problem in desc12. Checking in src/org/netbeans/modules/derby/JDKDerbyHelper.java; /cvs/db/derby/src/org/netbeans/modules/derby/JDKDerbyHelper.java,v <-- JDKDerbyHelper.java new revision: 1.5; previous revision: 1.4 done
The current state is compliant with JDK 6 update 3, so closing.