Server: Debian (Lenny/Sid)
Installation Method: tar.gz
I downloaded Openfire 3.7.1 (the tar.gz) and used it to upgrade my test box from 3.7.0. I do this by the following steps.
-
shutdown Openfire
-
extracting openfire_3_7_1.tar.gz to an “openfire_3_7_1” directory
-
move symlink of “openfire” from openfire_3_7_0 to openfire_3_7_1
-
Copy ./bin/openfire, ./conf/openfire.xml, and ./resources/security/* from openfire_3_7_0 to openfire_3_7_3
-
restart Openfire
Above is how I have been updating Openfire since I took over this project (~Openfire 3.3.1). This time however, Openfire failed to start and I received an “install4j” error. I did a diff on the openfire_3_7_0 and openfire_3_7_1 directories and found the .install4j directory in the root of the 3_7_0 directory. I copied this over to the 3_7_1 directory and then Openfire started fine.
My question is, was the exclusion of the .install4j directory an oversight or is this going to be the norm for future versions?
-dweez