I'm attaching a little script, entitled "c", I wrote that does both the Maven
assemble and the ant compile. I execute this every time I make a change to a
"source" object - that is, any object that resides under the {dspace-source}
directory. This includes .jsp .java messages.properties, etc - any object
that lives in the {dspace-source} directory. I also have another script,
entitled "cc" that does the exact same thing as this one, except that it does a
"mvn clean package" instead of "mvn package". The purpose of these scripts is
just to save me some typing, i.e., I only have to type "c" instead of the mvn
and ant commands, and it does the directory changing so I can just execute this
script from under {dspace-source}.Every time I execute this script, I then have to restart my web server (we use Sun Webserver7) in order to have my changes picked up by the web application. Note: Any time I change dspace.cfg (or any other object in my /dspace installation directory), I do NOT have to execute this little script - I only have to restart my web server for my changes to be picked up. Hope this helps, Sue Sue Walker-Thornton Software Developer/Database Administrator NASA Langley Research Center|LITES Contract (757) 224-4074 -----Original Message----- From: glit...@eng.ucsd.edu [mailto:glit...@eng.ucsd.edu] On Behalf Of Glenn Little Sent: Wednesday, February 09, 2011 1:46 PM To: Thornton, Susan M. (LARC-B702)[LITES]; dspace-tech@lists.sourceforge.net Cc: amutsikiwa Subject: Re: [Dspace-tech] modifying config dspace.cfg Okay, I'm really confused now. These two replies are *both* different from the (itself confusing) description at: https://wiki.duraspace.org/display/DSDOC/Configuration#Configuration-UpdateReminder The above page does not mention running mvn at all. Where does that come from? The above page also explicitly recommends not just editing the runtime config file. What's confusing about that page itself is that it first says, essentially, to edit [dspace-source]/dspace/config/dspace.cfg, then cd to the target/dspace-<version>-build.dir and run "ant update_configs. But then it goes on with to suggest running either (or both?) of "ant -Dconfig=[dspace]/config/dspace.cfg", and "ant init_configs". I'm having trouble really understand the conditions under which you would run one or the other of those, and how those tie in with the initial "ant update_configs". Let alone how those all tie in with the two suggestions given previously in this thread. Can anyone help unconfuse me? Thanks! -glenn On Wed, Feb 9, 2011 at 8:43 AM, Thornton, Susan M. (LARC-B702)[LITES] <susan.m.thorn...@nasa.gov> wrote: > Here is the process I follow and never have any problems. > > During the initial install/implementation of your DSpace instance, you will > make your changes to dspace.cfg in {dspace-source}/dspace/config. Then once > you do a "fresh-install", your /dspace directory is populated with all other > sub-directories like /bin /config /etc /lib /webapps, etc. > > From this point on, the place to make your changes to dspace.cfg is in your > dspace installation directory, NOT the source directory. If you do not make > your changes in /dspace/config/dspace.cfg, your changes will not be picked > up. Also remember that you have to stop and start your web server before > these changes will be picked up too. > > Hope this helps, > Sue > > > > Sue Walker-Thornton > Software Developer/Database Administrator > NASA Langley Research Center|LITES Contract > (757) 224-4074 > > > > -----Original Message----- > From: amutsikiwa [mailto:amutsik...@uzlib.uz.ac.zw] > Sent: Wednesday, February 09, 2011 7:25 AM > To: 'Glenn Little'; dspace-tech@lists.sourceforge.net > Subject: Re: [Dspace-tech] modifying config dspace.cfg > > After making changes to [dspace-source]/dspace/config/dspace.cfg, change > directory to [dspace-source]/dspace/ and then run > mvn -e -o packages > Then change directory to > [dspace-source]/dspace/target/dspace-1.7.0-build.dir > And run > ant -Doverwrite=true update clean_backups > > > The changes should be effected. > > > Regards, > > Admire Mutsikiwa > University of Zimbabwe > > -----Original Message----- > From: Glenn Little [mailto:lit...@cs.ucsd.edu] > Sent: Wednesday, February 09, 2011 2:00 AM > To: dspace-tech@lists.sourceforge.net > Subject: [Dspace-tech] modifying config dspace.cfg > > I've got an install of dspace and am now trying to modify the > dspace.cfg file. But I'm confused as to which file to edit. I > thought I was supposed to do this: > > + edit [dspace-source]/dspace/config/dspace.cfg > > + change dir to [dspace-source]/dspace/target/dspace-1.7.0-build.dir > > + ant update_configs > > The problem is that this does not do anything with my new changes. > Instead it puts an old copy of my dspace.cfg file over into > [dspace]/config/dspace.cfg.new. As far as I can tell, that *old* copy > comes from: > > [dspace-source]/dspace/target/dspace-1.7.0-build.dir/config/dspace.cfg > > So what is the real intent of the copy in dspace-<version>-build.dir > compared to the one higher up in the source tree? How is one *really* > supposed to update the configuration, post-install? > > Thanks... > > -glenn > > ---------------------------------------------------------------------------- > -- > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech >
c
Description: c
------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
