On Wed, Jan 19, 2011 at 11:47:48AM -0300, Sergio Belkin wrote: > Hi,, > > I've read on documentation of v1.5.1: > > Note that this does mean there are multiple copies of the compiled DSpace > code and third-party libraries in the system, so care must be taken to > ensure that they are all in sync. (The storage overhead is a few megabytes, > totally insignificant these days.) In general, when you change any DSpace > code or JSP, it's best to do a complete update of both the installation ( > [dspace]), and to rebuild and redeploy the Web UI and OAI .war files, by > running this in [dspace-source]: > > ant -D* [dspace]*/config/dspace.cfg update
If you enter that when in [dspace-source], Ant will complain that there is no build.xml. Here the documentation is in error. Thanks for discovering that. It's also incorrect in that the command should be: ant -Dconfig=[dspace]/config/dspace.cfg update > and then following the instructions that command writes to the console. > > http://www.dspacedev2.org/1_5_1Documentation/ch09.html#N12F43 > > > However on Chapter 9 it states: > > 1. > > Re-install the DSpace WAR(s) to [dspace]/webapps by running the following > command from your > [dspace-source]/dspace/target/dspace-[version].dirdirectory: > > ant -Dconfig=* [dspace-source]*/config/dspace.cfg > update [dspace-source]/dspace/target/dspace-[version].dir is the correct directory. You should find a 'build.xml' there. Ant will assume that it is to get things relative to your current directory, and the 'config' property points to a file which will tell Ant where to put them. > > http://www.dspacedev2.org/1_5_1Documentation/ch09.html#N12F43 I don't find that text there. Was this meant to cite a different version of the documentation? > So my question is what's the right location where I should update: either > from "source directory" or "target directory"? The "target" in "[dspace-source]/dspace/target" is a different use of the word. Notice that it is beneath [dspace-source] so you are in the source tree. The build tool (maven) assembles a project into a directory "target" within that project's directory (sub)tree during the *build* procedure. This has no connection with [dspace] being the target of the *installation* procedure. The confusion of terms is unfortunate. -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgpA8Hq5tIbA9.pgp
Description: PGP signature
------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
