[
https://jira.duraspace.org/browse/DS-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27712#comment-27712
]
Bram Luyten (@mire) commented on DS-1489:
-----------------------------------------
--work in progress--
The result of this bug was that there were both solr-3.3.0 and solr-3.3.5 jars
in my local maven repository.
in dspace-oai/pom.xml the dependency on org.apache.solr solr-solrj was declared
on 3.3.0
similar, in dspace/modules/oai/pom.xml the dependency on org.apache.solr
solr-core was declared on 3.3.0 as well
Like this was recently change in dspace-api, I changed the version to
<version>${lucene.version}</version>
Right now, I don't think it's completely solved yet. Although I now only have
solr-3.3.5 jars in my directory, I still have multiple versions of lucene. all
of the lucene jars exist both as 3.3.0 and 3.3.5 in my directory.
starting up tomcat gives following complaints:
http://pastebin.com/wReNj1mr
> SOLRJ-3.3.0 dependency in OAI
> -----------------------------
>
> Key: DS-1489
> URL: https://jira.duraspace.org/browse/DS-1489
> Project: DSpace
> Issue Type: Bug
> Components: OAI-PMH
> Affects Versions: 3.1
> Reporter: Bram Luyten (@mire)
> Assignee: João Melo
>
> pom.xml in dspace-oai declares a dependency on solrj-3.3.0, which is
> incompatible with the fact that solr has been upgraded to 3.5.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
