Attached is a patch to resolve the problem with the Derby UI plugin where the network server can be started on multiple ports for the same Eclipse project and not being able to stop a running network server for a project.
I'd appreciate it is someone could review it, and if it looks okay, commit it.
The fix changes the behaviour to the following:
1) Only one network server can be started per project.
2) Once a network server is started for a project it must be stopped before any of it's settings (port, host and derby.system.home) can be changed.
3) If a user tries to change these settings when the network server is running they will be notified
that they cannot change them, and the text fields become uneditable.
Manually tested this scenario:
Started a network server for a project
Attempted to change the port for the project
This fails - the textfields are uneditable and a Pop-up box states the server must be stopped
Stopped the network server
Changed the port number
Restarted the network server on the new port number
Stopped the network server on this port number
Created a second project and modified the port number to be the same as the
server running on the first project.
The console window explains this fails because a server is already running on this port.
Output from svn stat: