[
https://jira.duraspace.org/browse/DS-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21454#action_21454
]
Tim Donohue commented on DS-980:
--------------------------------
Hi Kevin. One quick question for you:
Is there a reason that the
http://scm.dspace.org/svn/repo/modules/dspace-solr/branches/dspace-solr-parent-3.3.0.0
branch hasn't been merged into
http://scm.dspace.org/svn/repo/modules/dspace-solr/trunk/ (just noticed their
pom versions are completely different, etc)? Is it just because you wanted
some more testing of 3.3.0.0 first?
Obviously it isn't a big deal, I just know eventually we will need to merge
that branch into dspace-solr/trunk, and then release 3.3.0.0 version based on
that dspace-solr/trunk code. That will just ensure dspace-solr/trunk doesn't
end up out-of-date.
I've installed the patch (after installing dspace-solr 3.3.0.0 locally), and
everything has built fine. Now time for some testing of the browse/search
functionality! I'll let you know how it goes (obviously).
> 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 contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
