All,
Juven is changing the App Booter to reuse the prepackaged classworlds.conf. This means we will no longer be using the PlexusContainerHost, which allows us to send control commands over a port ( to stop nexus, etc).
Previously we used nexus's stoft stop 'feature' to programatically copy new nexus configuration files into place.
Nexus doesn't have this 'feature' anymore, and we are not using the PlexusContainerHost, so we cannot put it there. Which leaves us hard stopping Nexus for each test. Which most of the time will be spent Forking a VM and brining up Nexus.
Velo had an idea to work around this, we could create a Nexus-IT-plugin for nexus that can reload the config, which would programatically clear the caches of the configuration utilities.
We also have a condition where we may need to remove the work dir, this plugin 'could' do this too.
What if nexus gets in an invalid state?
At the start of each test the Test harness should check the state of nexus, by hitting the status URL using the admin user/pass. If this is successful we don't need to do anything, if not, we will kill the currently running nexus and start a new one.
Problems and or suggestions?
