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.
[#200511211900, jdk1.5.0] When the AS 8.2 is added to Nb with already installed Derby from UC, it changes the derby.system.home (AKA Database Location) but it breaks all previoulsy created Derby connections and user losts contact with these database. I would suggest to use current derby.system.home to avoid users from this experience.
derby module issue I think.
Again, the derby from AU center is NOT in the NetBeans 5.0 plan, so I would say, not a bug if the bug was assigned to me :-)
not sure at all about fix-in-50 status... AUC derby is not in the plan
Agree the autoupdate module is not in the plan, no committment to fix this. I suggest removing fix-in-50 and adding the NO50 keyword to indicate this does not affect the release.
I can reproduce it with manually downloaded/reistered Derby and Derby Support module from daily builds and it is supported scenario from my point of view.
In that case I agree that this is a valid bug and should be addressed in the Derby module somehow.
Not a bug in the Derby support module: 1. The Derby support module only provides the API to change derby.system.home. It's up to the API client how it uses this API and the Derby support module can't do anything about it. 2. The appserver plugin doesn't need to change derby.system.home anymore, since only reason for it was to register its sample databases.
Fixed
v.