Re: [Dspace-tech] again problems with build.properties, dspace.cfg and install directories
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: bluy...@gmail.com [mailto:bluy...@gmail.com] On Behalf Of Bram Luyten
Sent: 14 January 2014 11:46
To: Brouns, Francis
Cc: dspace-tech@lists.sourceforge.net
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:image002.jpg@01CF1200.BBBDECC0]
Bram Luyten +1 202 684 6365
2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010
Esperantolaan 4, Heverlee 3001, Belgium
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Mon, Jan 13, 2014 at 4:36 PM, Brouns, Francis
francis.bro...@ou.nlmailto:francis.bro...@ou.nl 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=119420431iu=/4140/ostg.clktrk
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.netmailto:DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette
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
--
[image: logo]
*Bram Luyten* +1 202 684 6365
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Wed, Jan 15, 2014 at 2:47 PM, Brouns, Francis francis.bro...@ou.nlwrote:
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:* bluy...@gmail.com [mailto:bluy...@gmail.com] *On Behalf Of *Bram
Luyten
*Sent:* 14 January 2014 11:46
*To:* Brouns, Francis
*Cc:* dspace-tech@lists.sourceforge.net
*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
--
[image: Description: Image removed by sender. logo]
*Bram Luyten* +1 202 684 6365
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Mon, Jan 13, 2014 at 4:36 PM, Brouns, Francis francis.bro...@ou.nl
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
Re: [Dspace-tech] again problems with build.properties, dspace.cfg and install directories
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: bluy...@gmail.com [mailto:bluy...@gmail.com] On Behalf Of Bram Luyten
Sent: 15 January 2014 15:51
To: Brouns, Francis
Cc: dspace-tech@lists.sourceforge.net
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:image001.jpg@01CF120C.683401A0]
Bram Luyten +1 202 684 6365
2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010
Esperantolaan 4, Heverlee 3001, Belgium
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Wed, Jan 15, 2014 at 2:47 PM, Brouns, Francis
francis.bro...@ou.nlmailto:francis.bro...@ou.nl 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: bluy...@gmail.commailto:bluy...@gmail.com
[mailto:bluy...@gmail.commailto:bluy...@gmail.com] On Behalf Of Bram Luyten
Sent: 14 January 2014 11:46
To: Brouns, Francis
Cc: dspace-tech@lists.sourceforge.netmailto:dspace-tech@lists.sourceforge.net
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:image002.jpg@01CF120C.514270D0]
Bram Luyten +1 202 684 6365tel:%2B1%20202%20684%206365
2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010
Esperantolaan 4, Heverlee 3001, Belgium
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Mon, Jan 13, 2014 at 4:36 PM, Brouns, Francis
francis.bro...@ou.nlmailto:francis.bro...@ou.nl 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
Re: [Dspace-tech] again problems with build.properties, dspace.cfg and install directories
Hi Francis,
I noticed your dspace.install.dir parameter is commented out:
# DSpace installation directory. This is the location where you want
# to install DSpace. NOTE: this value will be copied over to the
# dspace.dir setting in the final dspace.cfg file. It can be
# modified later on in your dspace.cfg, if needed.
#dspace.install.dir=/dspace
dspace.dir = d:/dspace/dspace32
build.properties needs dspace.install.dir and does not need dspace.dir.
Reference dspace 3_x build.properties:
https://github.com/DSpace/DSpace/blob/dspace-3_x/build.properties
Hope this helps!
Bram
--
[image: logo]
*Bram Luyten* +1 202 684 6365
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Wed, Jan 15, 2014 at 4:11 PM, Brouns, Francis francis.bro...@ou.nlwrote:
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:* bluy...@gmail.com [mailto:bluy...@gmail.com] *On Behalf Of *Bram
Luyten
*Sent:* 15 January 2014 15:51
*To:* Brouns, Francis
*Cc:* dspace-tech@lists.sourceforge.net
*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
--
[image: Description: Image removed by sender. logo]
*Bram Luyten* +1 202 684 6365
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Wed, Jan 15, 2014 at 2:47 PM, Brouns, Francis francis.bro...@ou.nl
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:* bluy...@gmail.com [mailto:bluy...@gmail.com] *On Behalf Of *Bram
Luyten
*Sent:* 14 January 2014 11:46
*To:* Brouns, Francis
*Cc:* dspace-tech@lists.sourceforge.net
*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
--
[image: Description: Description: Image removed by sender. logo]
*Bram Luyten* +1 202 684 6365
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Mon, Jan 13, 2014 at 4:36 PM, Brouns, Francis francis.bro...@ou.nl
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
Re: [Dspace-tech] again problems with build.properties, dspace.cfg and install directories
Hi Francis,
It looks like your local.properties file is incorrect. The very first
property in that file should be named dspace.install.dir. But, yours
says dspace.dir.
So, your local.properties file needs to have the same settings as the
default build.properties:
https://github.com/DSpace/DSpace/blob/master/build.properties#L25
This is exactly why you are seeing this line in the final dspace.cfg:
dspace.dir = ${dspace.install.dir}
Essentially that line doesn't get filled out cause there is no value for
dspace.install.dir in your local.properties file.
I hope that helps.
- Tim
On 1/15/2014 9:11 AM, Brouns, Francis wrote:
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:*bluy...@gmail.com [mailto:bluy...@gmail.com] *On Behalf Of *Bram
Luyten
*Sent:* 15 January 2014 15:51
*To:* Brouns, Francis
*Cc:* dspace-tech@lists.sourceforge.net
*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
--
Description: Image removed by sender. logo
*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=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Wed, Jan 15, 2014 at 2:47 PM, Brouns, Francis francis.bro...@ou.nl
mailto:francis.bro...@ou.nl 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:*bluy...@gmail.com mailto:bluy...@gmail.com
[mailto:bluy...@gmail.com mailto:bluy...@gmail.com] *On Behalf Of
*Bram Luyten
*Sent:* 14 January 2014 11:46
*To:* Brouns, Francis
*Cc:* dspace-tech@lists.sourceforge.net
mailto:dspace-tech@lists.sourceforge.net
*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
--
Description: Description: Image removed by sender. logo
*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=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Mon, Jan 13, 2014 at 4:36 PM, Brouns, Francis francis.bro...@ou.nl
mailto:francis.bro...@ou.nl 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
Re: [Dspace-tech] again problems with build.properties, dspace.cfg and install directories
Hi Tim and Bram,
thank you very much for spotting this. I could not find the differences.
best wishes, Francis
-Original Message-
From: Tim Donohue [mailto:tdono...@duraspace.org]
Sent: 15 January 2014 16:25
To: Brouns, Francis
Cc: 'Bram Luyten'; dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] again problems with build.properties, dspace.cfg
and install directories
Hi Francis,
It looks like your local.properties file is incorrect. The very first
property in
that file should be named dspace.install.dir. But, yours says dspace.dir.
So, your local.properties file needs to have the same settings as the
default build.properties:
https://github.com/DSpace/DSpace/blob/master/build.properties#L25
This is exactly why you are seeing this line in the final dspace.cfg:
dspace.dir = ${dspace.install.dir}
Essentially that line doesn't get filled out cause there is no value for
dspace.install.dir in your local.properties file.
I hope that helps.
- Tim
On 1/15/2014 9:11 AM, Brouns, Francis wrote:
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:*bluy...@gmail.com [mailto:bluy...@gmail.com] *On Behalf Of
*Bram Luyten
*Sent:* 15 January 2014 15:51
*To:* Brouns, Francis
*Cc:* dspace-tech@lists.sourceforge.net
*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
--
Description: Image removed by sender. logo
*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=servicesutm_source=emailfooterutm_
medi
um=emailutm_campaign=braml
On Wed, Jan 15, 2014 at 2:47 PM, Brouns, Francis francis.bro...@ou.nl
mailto:francis.bro...@ou.nl 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:*bluy...@gmail.com mailto:bluy...@gmail.com
[mailto:bluy...@gmail.com mailto:bluy...@gmail.com] *On Behalf Of
*Bram Luyten
*Sent:* 14 January 2014 11:46
*To:* Brouns, Francis
*Cc:* dspace-tech@lists.sourceforge.net
mailto:dspace-tech@lists.sourceforge.net
*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
--
Description: Description: Image removed by sender. logo
*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
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
--
[image: logo]
*Bram Luyten* +1 202 684 6365
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.comhttp://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml
On Mon, Jan 13, 2014 at 4:36 PM, Brouns, Francis francis.bro...@ou.nlwrote:
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=119420431iu=/4140/ostg.clktrk
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette:
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
--
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=119420431iu=/4140/ostg.clktrk___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
