Description of problem: Just to avoid any caching issues (which can avoided by deleting browser cache) we should move the revision # of several of the *.css and *.js files just in case there were changes. I know for a fact there were changes to the rhq-4.9.0.js file. This is a ten minute job and is low risk. [The corresponding CoreGUI.html and CoreGUI.gwt.xml files need to reflect the changes.] NOTE: This must be done only on the release/jon3.2.x branch as the master is already at the 4.10.0 revision and these should be different right now.
This is fixed with commit: 14605af0af9069 to rhq.git and release branch. Related productization commits are: f3774d2378d79 and 93209a10d31ee. Moving this to modified for testing in next brew build.
Moving to ON_QA as available for test with the following(or later) cumulative patch build: http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.1.GA/4-14-2014/ -Cumulative patch/update builds are applicable to 3.2.0.GA and later JON Server releases. -Cumulative patch builds should be tested with the 3.2.0.GA plugin pack contents until a newer plugin pack release is available.
Moving to VERIFIED. *.js, *.css files in question which are loaded from CoreGUI.html were renamed so that they would be reloaded. I checked using Firebug that after applying the patch the client browser sends GET request for those new *.js, *.css files. Tested on JON 3.2.1 GA 7 with CP1 (14-04-2014) applied (Build Number - 8b22dda:46a8e24)
JON 3.2.1 released week of 5/5/2014