On Tue, Feb 12, 2013 at 7:47 PM, Brian Freels-Stendel <[email protected]> wrote: > I'm looking at the ant build file, in order to write some documentation, and > I have some questions.
Hi Brian, that's great, thanks in advance. The Installation chapter indeed needs the most work, so this is greatly welcome. You probably know that, but don't forget to work in the 4.x space: https://wiki.duraspace.org/display/DSDOC4x/DSpace+4.x+Documentation > I'd like to add the test_database target to the help menu, since I've seen it > appear occasionally in the newsgroups, and there are a couple of comments and > messages I'd like to suggest updates to. I commited the change for you to the master branch (to be 4.0): https://github.com/DSpace/DSpace/commit/9f2a67c0aa8519ea04de3647eaf65fe8dd94ec35 > The update_code target backs up the bin, lib, and etc directories before > making new copies, but not the solr directory, which is only copied. Is this > satisfactory, or would it be better to treat the solr directory the same as > the others? I understand that it may be too big to want copies around, and > that only non-data files will be overwritten, but it's probably possible to > back up only those same non-data files if it's desirable. I wouldn't worry about the solr directory at all. The data can be recreated at any time using "update-discovery-index -b". It's just not necessary to back it up unless you worry about high availability and time of recovery. On a related note, I noticed that the search directory (the old Lucene index) is no treated the same way as the solr directory. It most likely should be. (Although it takes considerably longer to recreate). > I also have a local addition to my build file that allows me to copy custom > theme files from [dspace-src]/dspace /modules/xmlui/src/main/webapp to > [dspace]/webapps/xmlui. This was incredibly useful when I didn't have write > access to [dspace], since it avoided a maven build and Tomcat restart. (But > it did ensure that changes would be incorporated in future builds.) Would > this be a useful addition to wrap into the mix, or would it be better to > create a feature request and get feedback on it separately? Or is it > something that probably wouldn't be useful? I think it would be useful, but please create a ticket for it so that we can discuss it at a convenient time. Patch to go with is also most welcome. Thanks. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
