I had to upgrade from 12.10.1 to 12.10.2 and again had problems with it. (other than your server down today).
At tomcat server start, may I suggest that you:
- Test for the presence of a directory: /etc/xwiki (xwiki being the name of the tomcat xwiki.war)
- If it does not exists:
- Create it and copy all the configuration files you need.
- Create /etc/xwiki/lib (to put the driver libs needed for databases…)
- Copy (or check) /etc/xwiki/lib/* to $TOMCAT_HOME/webapps/xwiki/WEB-INF/lib
- Use the files here, and ignore those from the tomcat WEB-INF.
(This is not my idea, I see other tomcat apps do exactly this), and I think that it’s a few lines of code.
It would be good if you could provide an option in xwiki interface to (at least prepare) upgrade, which would allow to download the new war directly on the server (and maybe all dependent files and flavors…). It could install a small shell script to kill tomcat, do the needed cleaning and directory renaming and other needed stuff. And when everything is ready, provide a button to restart tomcat?
This way, you are sure that you have everything needed to upgrade the app onsite (I was blocked today to 30 minutes because the nexus.xwiki.org was offline or I had problems to contact it, and so, the upgrade failed 5 times), and the administrator would not need to connect to the server (say in 95% of the time which would be a huge progress).
This would also make xwiki really more professional app, that big companies will like because simpler and faster upgrade.
I hope that this suggestion will have support from others and that you can do it.
Thank you for your work.