hello everybody,
can anybody tell me how to apply this policy:
Allow only administrator to see the bitsreams of any item, otherwise kept its
files hide from all others
Regards:
Amjeeki
Hello,
I'm doing a clean test installation of dspace-1.7.0-rc2 from SVN
source. I'm getting this error when I run mvn package:
[INFO]
[ERROR] BUILD ERROR
[INFO]
As a workaround, I commented out dspace-discovery from pom.xml and I
was able to run mvn package and apt fresh_install succesfully (though
the build is not working yet for probably unrelated reasons):
Index: pom.xml
===
--- pom.xml
For the past 6 months or so we've had intermittent crashes; at this point we
seem to be going down once every 1-3 weeks. When this happens, tomcat is
still running and postgres is stopped. We restart both and everything is
fine until it happens again. We finally decided to move our monitoring
Did you try rebuilding in mvn with -U to make sure your getting the most
recent releases of artifacts?
Discovery is a dependency of xmlui but published into the maven repository
as an artifact, so sure, you can chose to not build it, it will
be retrieved from maven as a prebuilt artifact for you.
Hi helix84,
Two of us just ran tests on this (both on Windows 7 and on Mac OSX snow
leopard), and it seems to be building fine for both of us.
Can you verify your version of Java Maven meet the current recommended
1.7 Pre-requisites. See:
Hi all,
I have a rather queer problem. My newly created dspace log files are always
owned by user root, though they are affiliated with the group dspace. For
example:
~$ ls -l /dspace/log/dspace.log.2010-12-14
-rw-r--r-- 1 root dspace 1176 2010-12-14 10:50
/dspace/log/dspace.log.2010-12-14
What operating system are you running on? Typically you can set default file
creation permissions with umask settings and other OS-level configuration. I
recommend you look into those types of settings for the OS you're dealing with.
-Sands
On Dec 14, 2010, at 1:13 PM, amutsikiwa wrote:
Hi
I was very happy to bumb into this thread. I am experiencing the same
problems as Jason was experiencing. I checked on my solr.log.server in the
dspace.cfg file. It was set to ${dspace.baseUrl}/solr/statistics and I
modified it to http://localhost:8080/solr/statistics as directed below. I
On Tue, Dec 14, 2010 at 18:29, Tim Donohue tdono...@duraspace.org wrote:
Can you verify your version of Java Maven meet the current recommended 1.7
Pre-requisites. See:
https://wiki.duraspace.org/display/DSDOC/Installation#Installation-PrerequisiteSoftware
I'm running on Debian Lenny.
ii
Hello,
The URL for /solr/statistics is only used by DSpace itself, for generation of
statistics. It's not the URL that you use for viewing them. If you want to
view them, there should be a link for statistics on the bottom right of the
menu on the front of your DSpace installation.
In
On Tue, Dec 14, 2010 at 20:01, Richard Rodgers rrodg...@mit.edu wrote:
The component that looks iffy to me is maven. Any chance of trying with 2.2
or better?
The documentation says 2.0.8 is required.
I installed 2.2.1-5 from Debian Squeeze and built from SVN
successfully. Will you hunt down
Hi Helix84,
After talking to a few other DSpace developers, we are pretty sure the
problem is in our DSpace Maven settings. It sounds like you may have an
older version of the 'maven-war-plugin' which is what allows Maven to
build WAR files, and it is confusing our normal build process.
So,
I now successfully built dspace from trunk r5955 on a pure Lenny
system (i.e. back to maven 2.0.9-2). Thanks for the fix.
I'll do more testing of dspace itself tomorrow, sorry I missed the
official testathon.
Regards,
~~helix84
Actually, I just quickly tested your DSpace installation, and your statistics
are available at:
http://ir.uz.ac.zw:8080/dspace/statistics
or also
http://ir.uz.ac.zw:8080/xmlui/statistics
Depending on which front end you prefer to use.
Jason
On 2010-12-14, at 3:00 PM, Jason Nugent wrote:
Hi list,
Illegal AccessError has occurred when I posted an item through SWORD
to DSpace 1.7.0 rc1 with discovery cosumer setting.
This error has not occurred when I posted through jspui nor xmlui.
Also this error has not occurred when I posted through SWORD to
DSpace without discovery consumer
16 matches
Mail list logo
