Hi!
The change of http to https in pom.xml file (+ removal of appropiate
.m2 folders) seems to have fixed my problem. The problem had occurred
quite lately because the build was working ok about a week ago, but
this week we run into this problem.
By the way: I tested rebuild in 1.7.2 test
Hi All
Can you point us to the relevant pom.xml file on github and also reference
the line number where a change is needed.
Thx in advance.
Cheers
hg
*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
Hi,
This is the pom.xml:
https://github.com/DSpace/DSpace/blob/dspace-3_x/pom.xml
The sonatype URL modification is required in line 1200:
- urlhttp://oss.sonatype.org/content/repositories/releases//url
+ urlhttps://oss.sonatype.org/content/repositories/releases//url
Since we started it,
Thx *Kiriaki*
*See:
**http://wiki.lib.sun.ac.za/index.php/SUNScholar/Upgrading/DSpace/Release_Notes/3.2#Build_Issues
http://wiki.lib.sun.ac.za/index.php/SUNScholar/Upgrading/DSpace/Release_Notes/3.2#Build_Issues
for a permanent record.*
*Cheers*
*hg*
*Hilton Gibson*
Ubuntu Linux Systems
Hey Guys,
we are using LDAP at our institution and I would like to implement a
choice authority based on it. Has anyone of you ever done something like
that?
Best
Christian
--
Odd: I just moved my ~/.m2/repository/org/sonatype/oss/oss-parent
directory aside, ran 'mvn clean install', and it had no trouble using
http://oss.sonatype.org/content/repositories/releases/; to fetch
oss-parent.
But we may as well secure the connection. The cost is negligible.
I've submitted
I have the request to change the metadata field
“pu.date.graduation” to “pu.date.classyear”
Is this simply a question of changing the name in the database and making sure
that all references in config files are changed as well ?
Do I have to worry about rye search index ?
Monika
when I try to deploy /solr with tomcat I get:
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester.sax).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig
for more info.
I've looked at
Hi Monika,
yes, you have to worry about the search indexing and the browse indexing as
well if this metadata fields place any role in the browse.
You will need to re-index.
Regards,
Kostas
On Apr 4, 2014, at 6:46 PM, Monika C. Mevenkamp moni...@princeton.edu wrote:
I have the request to
Before this error takes place I see this in the log file:
Apr 04, 2014 3:27:49 PM org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO:
validateJarFile(/deepblue/dspace/repository/dev/webapps_dev/solr/WEB-INF/lib/jsp-api-2.1.jar)
- jar not loaded. See Servlet Spec 2.3, section
Hi, Jose, can you tell us the version numbers of the stuff in your stack? OS,
Java, Tomcat? Thanks!
--Hardy
From: Jose Blanco [blan...@umich.edu]
Sent: Friday, April 04, 2014 2:31 PM
To: Dspace-Tech
Subject: Re: [Dspace-tech] can't get /sorl deployed in
I just got it deployed, but I'm not sure it's working. I got it deployed by
(1) deleting jsp-api-2.1.jar from the solr lib area, since it was
complaining about it.
AND
(2)
removing
listener
listener-classorg.dspace.solr.filters.ConfigureLog4jListener/listener-class
/listener
from the
Is this all because I don't have tomcat 7.
-Jose
On Fri, Apr 4, 2014 at 4:00 PM, Jose Blanco blan...@umich.edu wrote:
I just got it deployed, but I'm not sure it's working. I got it deployed by
(1) deleting jsp-api-2.1.jar from the solr lib area, since it was
complaining about it.
AND
(2)
Hi Jose,
I think your problem is more or less conflicts between some DSpace libs and
some that Tomcat already has. For example, the one that you mention that you
deleted, the jsp-api one, is a library that Tomcat has as well. So, lib version
mismatching problem :)
I think that some other
So you are suggesting I get rid of
xml-apis-1.0.b2.jar
and add
listener
listener-classorg.dspace.
solr.filters.ConfigureLog4jListener/listener-class
/listener
back in?
What about the version of tomcat. According to the documentation I
need to have 7 but right now I have 5.5.26.
I just got rid of xml-apis-1.0.b2.jar, and it still did not like the listner.
-Jose
On Fri, Apr 4, 2014 at 4:37 PM, Jose Blanco blan...@umich.edu wrote:
So you are suggesting I get rid of
xml-apis-1.0.b2.jar
and add
listener
listener-classorg.dspace.
Yes, you can try that. Maybe you need to remove the “xercesImpl” jar as well.
Also, take a look in your tomcat directory for a folder named “endorsed”. There
are located some of these jars that usually conflict.
I think moving to Tomcat7 could be a wise choice.
Regards,
Kostas
On Apr 4,
Hi, I agree with Kostas, I think moving to Tomcat 7 will resolve these issues.
I suspect, given that you're using Tomcat 5.5, that you're using RHEL or CentOS
6? I'm in the process of setting up new staging and production boxes using
RHEL6, Tomcat 5.5 is the best I can get with Yum, so I'm
Hi, here's some of the back and forth from the dspace-devel archive:
http://sourceforge.net/p/dspace/mailman/message/31032016/
From: Jose Blanco [blan...@umich.edu]
Sent: Friday, April 04, 2014 3:54 PM
To: Pottinger, Hardy J.
Cc: Kostas Stamatis;
Do you know why version dspace 4.1 now requires tomcat 7? Someone
here told me that solr is doesn't really needed it? Is it for another
dspace webapp that needs 7. I just want to understand the reason for
7. I'm hoping it has to do with solr, because that would explain the
problem I'm seeing.
Thank you for the link. It sounds like solr uses some jars that can
only be loaded with tomcat 7 and higher, like jsp-api-2.1.jar, and so
we need to go to tomcat 7 for this reason. Right? I want to be able
to explain this clearly to the sysadmin that will be installing tomcat
7. The new solr
I think the primary argument for bumping up the DSpace-recommended Tomcat
version, as explained by Mark Wood in that attached mail list thread, is that
Tomcat 5.5 will very shortly be EOL. You really don't want to be building a
brand new server on top of an EOL stack. I'm certain your sysadmin
It looks like Tomcat 5.5 is already considered end-of-life:
https://tomcat.apache.org/tomcat-55-eol.html
In general, when something becomes end-of-life (Java, Tomcat, etc), the
DSpace Committers stop testing on it. Therefore, DSpace 4.x is
completely untested on Tomcat 5.5 (and we cannot
Hi, Jose, if you do elect to move to a binary install of Tomcat 7 on RHEL6,
this init script might come in handy:
https://gist.github.com/hardyoyo/9903387
--Hardy
From: Tim Donohue [tdono...@duraspace.org]
Sent: Friday, April 04, 2014 4:48 PM
To:
24 matches
Mail list logo
