Hi Bram, attached my local.properties file.
I'm running Windows 7 Entreprise, maven 3.10.0, ant 1.9.2, tomcat 6.0.37, Sun java SE 1.7.0_21 best wishes, Francis From: [email protected] [mailto:[email protected]] On Behalf Of Bram Luyten Sent: 15 January 2014 15:51 To: Brouns, Francis Cc: [email protected] Subject: Re: [Dspace-tech] again problems with build.properties, dspace.cfg and install directories Francis, can you send a copy of your local.properties file where you blank out anything sensitive like DB passwords? I will investigate and try to reproduce this behaviour on my end. Bram -- [cid:[email protected]] Bram Luyten +1 202 684 6365 2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010 Esperantolaan 4, Heverlee 3001, Belgium www.atmire.com<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml> On Wed, Jan 15, 2014 at 2:47 PM, Brouns, Francis <[email protected]<mailto:[email protected]>> wrote: Hi Bram, yes, that is correct. I use a local.properties that has a value for dspace.dir. When I performed a fresh install, the dspace.cfg in the target directory was created fine. Now I am in the position that the dspace.dir parameter is not copied at all, or is only copied to the other parameters based on dspace.dir, such as the assetstore dir, log dir etc. So at the moment dspace.cfg contains dspace.dir = ${dspace.install.dir} assetstore.dir = d:/dspace/dspace32/assetstore log.dir = d:/dspace/dspace32/log etc. All other parameters of local.properties are copied correctly, as as properties that I set in the [dspace-source]/config/dspace.cfg file (e.g. dspace.url = ${dspace.baseUrl}) Because the value of the dspace.dir is not set, files are copied into the wrong location, within the [dspace-source]/xxx/target directory instead of into the [dpsace] directory. The main problem is that this behaviour is not consistent. When I started with the installation, the dspace.cfg in the target directory was correct. I only had problems with the ant update_configs. Other days, everything went fine, but now whatever I try, the dspace.dir parameter is not set. Our server is running under Linux, so I do not necessarily have to fix these problems that seem to be Windows related. And I do have a Dspace 1.8.3 and a version of Dspace 3.2 running on my Windows laptop, from the times that I managed to install correctly. But I would like to be able to update as I need to test out the update from 1.8 to 3.2 as well as explore new features and explore the switch from the current jspui to xmlui. best wishes, Francis From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Bram Luyten Sent: 14 January 2014 11:46 To: Brouns, Francis Cc: [email protected]<mailto:[email protected]> Subject: Re: [Dspace-tech] again problems with build.properties, dspace.cfg and install directories Hi Francis, from the look of your ant output, it looks like maven has not succeeded in correctly specifying the path. If I'm not mistaking, the -Denv=local forces maven to look for parameters in a local.properties file instead of your build.properties file. Can you confirm that your path is correctly specified in a file called local.properties and that you're not relying on the changes in the file build.properties? hope this helps, Bram -- [cid:[email protected]] Bram Luyten +1 202 684 6365<tel:%2B1%20202%20684%206365> 2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010 Esperantolaan 4, Heverlee 3001, Belgium www.atmire.com<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml> On Mon, Jan 13, 2014 at 4:36 PM, Brouns, Francis <[email protected]<mailto:[email protected]>> wrote: Hi all, I'm trying out a DSpace 3.2 install and update on a Windows machine and encounter many problems. Our server will be running on Linux, but I'm looking into new features using my own laptop, running Windows 7. Today I finished our JSP customisations, copied those into the [dspace-source] directories as usual, ran a mvn -Denv=local -U clean package from [dspace-source]/dspace, followed by a ant update from target\dspace-3.2-build. Again my [dspace]/config/dspace.cfg is not updated, nor is the backup file created or are any of the customisations present. Strangely enough, in the target directory an directory called ${dspace.install.dir} has appeared. This directory contains the subdirectories commonly found in the [dspace] directory. I did not pipe output from mvn to a file, so do not have that log anymore, but I have the log of the ant update command (see attachment). This process is rather unpredictable, like I explained in my earlier message. best wishes, Francis Brouns Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan en gebruik door anderen is niet toegestaan. Open Universiteit sluit iedere aansprakelijkheid uit die voortvloeit uit elektronische verzending. Aan de inhoud van deze e-mail en/of eventueel toegevoegde bijlagen kunnen geen rechten worden ontleend. This e-mail is intended exclusively for the addressee(s), and may not be passed on to, or made available for use by any person other than the addressee(s). Open Universiteit rules out any and every liability resulting from any electronic transmission. No rights may be derived from the contents of this message. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected]<mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ________________________________ Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan en gebruik door anderen is niet toegestaan. Open Universiteit sluit iedere aansprakelijkheid uit die voortvloeit uit elektronische verzending. Aan de inhoud van deze e-mail en/of eventueel toegevoegde bijlagen kunnen geen rechten worden ontleend. This e-mail is intended exclusively for the addressee(s), and may not be passed on to, or made available for use by any person other than the addressee(s). Open Universiteit rules out any and every liability resulting from any electronic transmission. No rights may be derived from the contents of this message. ________________________________ Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan en gebruik door anderen is niet toegestaan. Open Universiteit sluit iedere aansprakelijkheid uit die voortvloeit uit elektronische verzending. Aan de inhoud van deze e-mail en/of eventueel toegevoegde bijlagen kunnen geen rechten worden ontleend. This e-mail is intended exclusively for the addressee(s), and may not be passed on to, or made available for use by any person other than the addressee(s). Open Universiteit rules out any and every liability resulting from any electronic transmission. No rights may be derived from the contents of this message.
<<inline: image002.jpg>>
<<inline: image001.jpg>>
local.properties
Description: local.properties
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
