Hi all,
the manual still has:
PostgreSQL 7.3 or 7.4
PostgreSQL can be downloaded from the following location:
http://www.postgresql.org/ [http://www.postgresql.org/] Its
highly recommended that you try to work with Postgres 8.x or greater,
however, 7.3 or greater should still work.
As for 7.4
Hi Pons
Did you get a fix for this ? My upgrade just failed with same error ☹
Aaron Hossain
Senior Information Specialist
Central Server Group
Information Services
University of Abertay Dundee
Tel: 01382 308802
Mob: 07791670579
a.hoss...@abertay.ac.ukmailto:a.hoss...@abertay.ac.uk
Home of
Hi Aaron,
It seems as though your JSPUI webapp is still trying to use the 1.5.2
version of dspace-api -- have a look in the WEB-INF\lib folder of your
deployed webapp, and if you see files like dspace-api-1.5.2.jar and
dspace-jspui-api-1.5.2.jar, it means you're trying to run 1.6 JSPs on 1.5.x
Yes this did work! Thanks!
For some reason the copy of webapps did not take the all the files, I wiped and
did again and presto !
From: Kim Shepherd [mailto:kim.sheph...@gmail.com]
Sent: 25 June 2010 12:10
To: Hossain, Aaron
Cc: dspace-tech@lists.sourceforge.net; ponerulappa...@cognizant.com
Hi Flavio,
On 6/24/10 6:26 PM, Flavio Botelho wrote:
I dont have the code here with me, but a wild guess would be that uid
isnt the field that stores the complete DN.
ldap.id_field = uid
I was under the assumption that this field was used to initially search
the tree to find the user's dn,
Dear DSpace community-
The DSpace Global Outreach Committee is updating the Who's Using DSpace
registry, the most popular page on the DSpace website. Our goal is to keep
everyone's repository information updated to help facilitate connections
between users and to foster collaborations in the
We're currently running dspace 1.3.2 and would like to start the process of
upgrading to the current version. I found the instructions for doing this here:
http://www.dspacedev2.org/1_5_1Documentation/ch04.html#N10F6E
It says to copy the postgresql.jar file from the new package to the current
Hi,
I'm struggling with some dates issues and looking for help.
Dates held in the metadatavalues table are converted from their local time zone
to UTC before being stored in the database. The problem is that they are not
generally converted back to their local time zone before being displayed
On Fri, 25 Jun 2010, TAYLOR Robin wrote:
Dates held in the metadatavalues table are converted from their local
time zone to UTC before being stored in the database. The problem is that
they are not generally converted back to their local time zone before
being displayed (see Jira
Hello Karen,
you do not need to perform each step while performing an update over
several versions.
Just pay attention to all the changed prerequisites, configuration
parameters, initial scripts (e.g. like the browse initializatin) and
perform all the database upgrade steps between the
Hi folks,
Just to confirm, does DSpace perform a two step check and then bind for
authentication? I ask, because I've been talking to the fellow who has
access to our LDAP server logs and he has informed me that it appears as
though DSpace is attempting to bind with uid=jnugent,dc=unb,dc=ca,
Thanks for the help Tim and Peter.
@Tim: Yes, I noticed that ant update_configs produced .new files and I
had to manually merge them. This was mentioned after ant target was
completed, so that's helpful.
@Peter: Not sure if we need to do maven package for updating DSpace
configuration. I just
Looking at the code:
http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.6.0/dspace-api/src/main/java/org/dspace/authenticate/LDAPHierarchicalAuthentication.java
The place where the problem is ocurring seems bizarre..
It is as if ldap.search_scope was not being found in the config file?
Kudos,
Aha! I now realize what it is. The ldap.search_scope value is
commented out by default in the config file. I mistakenly believed that
this implied a default value of 2. If you leave the value commented out
and enable Hierarchical LDAP authentication, you generate a
NullPointerException.
All
14 matches
Mail list logo