These conf files (e.g. rhq-server-env.sh/bat and rhq-agent-env.sh/bat) would be sourced by the respective start scripts This will allow users to externalize JVM, debug, etc. settings and easily migrate them when upgrading to a new version of JON, rather than having to merge their changes into the potentially updated start scripts.
Agent half of this is done - r1111.
server half of this will have to wait for 1.2
do not touch the way the agent configures its env vars anymore - we now have the agent plugin able to modify the config and it requires things to be the way they are now (-env.bat.sh). agent auto-update also keeps these -env scripts so they are maintained during upgrades
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-590
ips, mazz - what (if anything) else needs to happen for this BZ?
nothing left to do on the agent side. the server configuration is different depending on if you are on Windows or UNIX platforms (because of the usage of Java Service Wrapper on Windows) so its not going to be trivial to get the server to be easily configurable in the same way for both Windows and UNIX anyway. I say we close this. The agent configuration was done but I don't think we need to do this for the server. The agent is the thing we most wanted to make it easier for upgrades and we did that.
Closing, we're not doing this.