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.
The update center has a module called Bundled Apache Derby Database. This should be updated to Java DB.
The module currently bundles Derby 10.1.1.0, thus it should not be called Java DB. We could upgrade to a Java DB build and rename the module. Petre, what do you think? Is a final Java DB build available?
I don't think there is a platform independent download of Java DB that we could use. Moreover, this is a Dev update center only, will not be on the beta/stable UC. So I don't think it is important to change the name to Java DB.
Closing as INVALID then.
So the module available from the real update center will be the Derby module? If there will be no Java DB build for download, it means that for people who want a db without installing the app server, we should tell them to download the Derby module from the update center. And it will be called Java DB in Tools menu? [i just did this and it is called Java DB in Tools menu] So after installing the module, we should tell them to start the db by choosing Tools > Java DB > Start Java DB? I just want to make sure that this is the correct way to document this.
The module bundling Derby won't be available on the beta and stable update centers. For people who don't want the appserver the official recommendation until now was to download a Derby binary from http://db.apache.org. So don't document downloading the module, because I don't think we intend to change this for 5.5 (the module will only be on the alpha update center). Petre?
Andrei is correct, treat this AU module as if it did not exist.