On Fri, Oct 04, 2013 at 01:07:37PM +0000, Pottinger, Hardy J. wrote: > Perhaps it would be helpful if we all shared how we manage our > various configurations? I know some people keep them in a private > git repository, with each environment being a branch, and then check > out this config folder and pass it in to Maven with a command line > option (-Dconfig= I think, but I don't use it so I don't know). I > rely solely on the -Denv= option myself. I think if we have a better > idea of how we use the tools in practice, we'll better understand > why we are proponents of the differing views of the build.properties > file.
Most of the instances I work with are development/bug fix, and I tend to name them by the Jira ticket, because I usually have several cooking at once, so I'd have to create a new build.properties every time. Thus I usually ignore build.properties altogether. Instead I copy the stock config/dspace.cfg to ~/dspaces/configs/DS-nnnn.cfg and edit it to suit, setting dspace.dir = /home/mwood/dspaces/DS-nnnn. 'createdb DS-nnnn' followed by 'ant fresh_install -Dconfig=/home/mwood/dspaces/configs/DS-nnnn.cfg' sets it up. Drop a new Context descriptor file into /etc/tomcat-7/Catalina/localhost and it should be running. When I build a DSpace for production, I go to the server, check out and build a copy of the appropriate project from our local code repository (SVN, moving to an institutional instance of GitHub), merge our local configuration values into a copy of the new stock dspace.cfg if it's a version upgrade, and 'ant update -Dconfig=wherever-I-put-it'. This doesn't happen often. Perhaps there's a way to just copy target/ from my workstation to the server and 'ant update' from it. The configuration has historically been so tangled up in various steps of the build/install/run process that I at first feared to mess with the sequence, and later grew too lazy to look for a better way. Time to wake up.... We've attempted to keep production config/ trees in SVN, but we don't do this often enough to develop the habit so commits have been a bit spotty. You can perhaps see why I would like to have a clean separation between build and install. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
