A little more generally: you need to read the upgrade instructions for every version between the one you start with and the one you are going to, and carry out all of the unique upgrade instructions along that path. That is, some things (like .war files) are replaced each time, and you can just replace them once with the latest version; other things (such as database schema and configuration) receive cumulative changes and you must apply each version's changes.
This may seem like a lot of work, but I've been through it and I think it sounds worse than it is. There's been some discussion recently recommending that, rather than edit new sections into your existing dspace.cfg, you should edit your existing local settings into a fresh dspace.cfg from the version you want to wind up at and then review it for any additional settings you may wish to make. Large sections of dspace.cfg were reorganized in 1.5.1 and this method should save you a lot of error-prone tedium. Plus you only have to edit the file once, and don't have to merge lots of little changes from various versions. -- Mark H. Wood, Lead System Programmer [email protected] Friends don't let friends publish revisable-form documents.
pgpYHr63GaYLo.pgp
Description: PGP signature
------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
