[
https://jira.duraspace.org/browse/DS-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21671#comment-21671
]
Tim Donohue commented on DS-980:
--------------------------------
Ok, I'm now satisfied that this patch works.
However, I have one final question/concern.
With the release of Solr 3.3, do we still need the 'dspace-solr' project?
According to the README
(http://scm.dspace.org/svn/repo/modules/dspace-solr/trunk/README), this
'dspace-solr' project is a customized version of Solr which includes the
following patches:
* http://wiki.apache.org/solr/FieldCollapsing (INCLUDED IN Solr 3.3)
* http://blog.jteam.nl/2009/10/20/result-grouping-field-collapsing-with-solr/
(SAME AS SOLR-236)
* https://issues.apache.org/jira/browse/SOLR-236 (INCLUDED IN Solr 3.3)
So, it looks like our custom "patched" version of Solr may no longer be
necessary?
Would it be possible to switch our dependencies over to just utilize Solr 3.3.0
in Maven Central: http://repo1.maven.org/maven2/org/apache/solr/solr/3.3.0/ ?
In my mind, it's a good thing if we can stop creating our own custom release
called "dspace-solr". I'd much rather use the Apache Solr release in Maven.
> Upgraded solr & lucene to version 3.3.0
> ---------------------------------------
>
> Key: DS-980
> URL: https://jira.duraspace.org/browse/DS-980
> Project: DSpace
> Issue Type: Improvement
> Components: Discovery, DSpace API, JSPUI, Solr, XMLUI
> Affects Versions: 1.8.0
> Reporter: Kevin Van de Velde
> Assignee: Tim Donohue
> Priority: Major
> Attachments: Lucene_&_Solr_version_upgrade_to_3_3_0.patch
>
>
> Since DSpace is still using solr 1.4.x & lucene 2.9.3 I have created a patch
> that will upgrade these to version 3.3.0 (Lucene & solr have received
> matching version numbers).
> Since the dspace solr also requires a LocalHostRestrictionFilter I have
> created a dspace-solr module with version 3.3.0.0 at the following location:
> http://scm.dspace.org/svn/repo/modules/dspace-solr/branches/dspace-solr-parent-3.3.0.0
> Because of the new dspace-solr module a local installation of this module is
> required to actually test the patch (once the patch has been tested this
> module will need to be deployed).
> Also a thing to note, the solr upgrade just required updating the poms, but
> for Lucene some code had to be rewritten some extra eyes on this wouldn't
> hurt (although the tests I performed have been successful).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it.
http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
