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 a start a registered instance of GlassFish, ~/.netbeans-derby gets created without regard to my choice of netbeans userdir. There should be an option to define its location, or it should be relative to the userdir (preferrably inside it). The impact of this is not high obviously, but the annoyance factor is tremendous. Thus P2. -- I'm working with NetBeans IDE Dev (Build 200610231500, C/C++ Pack 20061108) 1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b102 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251
The file is in $HOME instead of the userdir because folks need to delete their userdir to overcome IDE bugs. If the DB was placed in the userdir, users would need to remember to save their java db data before they delete the userdir. Eventually, every user will forget this "rule" and lose data and schemas that they really wanted to keep. By putting the data in $HOME we are making it just a bit harder to make this mistake
Isn't it possible to put it next to the current userdir? This would make things a little bit easier. E.g. I'm using two different NBs - 5.5 and the latest 6.0. Obviously both of them are using ~/.netbeans-derby . Luckily for me, I'm using j2ee stuff only from one of these, but if I were not - it would be a breeding ground for various conflicts. Reopening.
It is technically possible to make the Derby database directory (.netbeans-derby) a sibling of the userdir. However, I'm not sure it is the right thing to do, since if you had two userdirs in two different parent directories (as in .../parent1/userdir1 and .../parent2/userdir2), two .netbeans-derby directories would get created (with two sample databases, two Visual Web Pack travel databases, etc.). This might or might not be what an user wants. Morever, the location of the database directory can be changed in Options - Advanced Options - Server and External Tool Settings - Java DB Database - Database Location, thus downgrading to P3. Actually I would close this issue, because what you required in the initial description ("an option to define its location") is already supported.
> Morever, the location of the database directory can be changed in Options - > Advanced Options - Server and External Tool Settings - Java DB Database - > Database Location, thus downgrading to P3. Actually I would close this issue, > because what you required in the initial description ("an option to define its > location") is already supported. In this case I'm OK with closing the issue. Having the ability configure the location is exactly what I was expecting. -> INVALID