On May 16, 2008, at 7:26 AM, Blanco, Jose wrote: > I'm planning on having the 1.5 dspace code for 1.5 installed in > multiple > directories pointing at a particular repository directory ( where > dspace.cfg lives and the assetstore). For example: > > /dspace-dev-source using the /dsace-dev-repository > /dspace-prod-source using the /dspace-prod-repository > /dspace-blancoj-source uinsg the /dspace-dev-repositoyr > > This is the way I had things setup for 1.4.2. > > Now that in 1.5 we are using maven, if I want to build the code for > any > of these areas, I assume I just follow the instructions, and say I > want > to build /dspace-dev-source, I do this: > > cd /dspace-dev-source/dspace/; > mvn package > > cd /dspace-dev-source/dspace/target/dspace-1.5-build.dir/; > ant -Dconfig=/dspace-dev-repository/config/dspace.cfg update
Yes, this will work initially... However, I recommend that you'll even want o be maintaining your configs changes in that original / dspace-<stage>-source and that this would include your /dspace- <stage>-source/configs/dspace.cfg, if you do it this way, then you don't need the -Dconfig and instead you would run "init_configs" instead... > cd /dspace-dev-source/dspace/target/dspace-1.5-build.dir/; > ant init_configs update > and then move the webapp dir to the appropriate tomcat dir etc.... why not just add a <Host> entry in your tomcat server.xml for each of your /dspace-<stage>-repository/webapps? Then you don't need to move anything. > I've done this just fine with one source directory, but when I have > multiple ones, is this the way it will work? > > I also had to install a jar file for the the one source dir I > worked on, > and I will need this jar file in the other source dirs, so I assume I > will have to do the same install for each source dir? The same maven repository would be used in each build, so I assume you will be fine installing it once. > I will look around for some documentation on maven to try to better > understand it, but if any one knows of a good site, please let me > know. I think your approach is sound. But I do fear you may find yourself moving changes back and forth between your stages an awful lot, and this may turn out to be arduous... Using a svn repository, branching and tagging, might save you from that pain of tracking your customizations across the stages. Cheers, Mark ~~~~~~~~~~~~~ Mark R. Diggory - DSpace Developer and Systems Manager MIT Libraries, Systems and Technology Services Massachusetts Institute of Technology ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
