Some of your install specific info will be in the jforum-custom.conf file (under the WEB-INF/config directory).
However, if you are making codes changes to the .htm pages, templates, etc., those would have to be redone with each update ... or a smarter way would be to keep a copy of those modified files in a different location. Then after any updates, review the new files for any new changes, and if there aren't any, you should be able to just copy over your modified files. Of course, if there are significant changes, you would have to "merge" those with yours.
But yes, this is a problem with making your own custom changes to any application that gets updated from the vendor (or other sources).
In a corporation customized version, it would be acceptable to change these things, I think so.
So, I ask you: somebody here that already did it, has some recomendation to do these modifications (and every others) by a smart way?
The best in this case to do would be to move the texts into configuration files, with defaults for old installations with old configuration files.
However I have the same problem. Since my changes won't go into the JForum CVS, I have to make my own CVS, using modified code from JForum. Perhaps there's support in CVS for doing so. I don't know yet.
[originally posted on jforum.net by Per Johansson]
I use a tool like winmerge or beyondcompare to copy my changes from one version to the other. These tools mae it quite easy to identify the changes. The best way of doing it is to compare the original version with the changed one to identify the modified files and than to compare the new version with your modified files only....
Sven [originally posted on jforum.net by Anonymous]
I agree with Anonymous here. If you perform a diff -c, then you can use patch to almost always get a perfect release update. This assumes that your mods are modest, and the update not extensive. However, at the very least, your diff output gives you a very concise recipe for manually updating the new release. [originally posted on jforum.net by time]
I agree with above, but the easiest way I have found so far is to use netbeans5, it has good CVS support for merges etc, and a real nice graphical diff tool. 5 is still beta but nearly done for release.
I regularly grab CVS version of JForum just to keep them in step, i.e. frequent merges are smaller and therefore easier to manage, as well as getting all the jforum bug fixes. :lol: [originally posted on jforum.net by MrNice]
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop