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 removed from Nb with already installed Derby from UC, the Derby folder from UC should be used as 'Derby Location' and 'Driver File(s)' location. Otherwise, after the AS uninstallation, it will lead to broken Derby drivers registration. Logicaly rollback the changes described in issue 69094.
When you say 'remove', do you mean you unregister the server instance, but you do not uninstall the AS 8.2 bits from disk? If it's only unregister, the user might still want to use the very db from the AS 8.2 bits, without working with a server instance...No?
I would not expect that user which registered both Derbyy, then kick off the AS, wants to use the AS Derby installation :-). But if you ensure that after AS uninstaltion the drivers registration will be fixed I don't have proble with such behaviour.
no Derby on AU, so either we unregister the as8.2 derby implementation when the last AS8.2 or AS 9.0 server domain is unregistered from the IDE, or I would prefer we keep it until the App server is physically unistalled . What do you think?
It does not depend on AU. It is reproducible with manually downloaded/registered Derby. We can keep the AS Derby .jars until the App server is physically unistalled, but how Nb identify that the AS was physically unistalled? Unregistration the AS8.2 derby implementation when the last AS8.2 or AS 9.0 server domain is unregistered from the IDE sounds much easier to me.
The plugin does not change any more the derby home if it is already set. So a sequence of adding/removing an 8.2 server, if derby is already configured will be a nop.
v.