[ 
https://issues.apache.org/jira/browse/LUCENE-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Willnauer updated LUCENE-1407:
------------------------------------

    Attachment: LUCENE-1407.patch

Moved
- org.apache.lucene.search.RemoteSearchable.java
- org.apache.lucene.search.RemoteCachingWrapperFilter.java
and depending test-cases to contrib/remote

Removed ant#rmci call from build.xml
Added build.xml to contrib/remote
Added pom.xml.template to contrib/remote
Added package.html to contrib/remote/src/java/org/apache/lucene/search/

Ideally, the move should be done using svn copy which does not appear in a diff 
afaik.

I did run test-cases with success. 
After finishing the patch I removed the Java standard library and compiled 
against android.jar version 1.1 / 1.5 and did not get any compile errors.
I did not run the build in an emulator neither did I run any test-cases in it I 
guess that is little out of scope but I will do it one in the near future just 
in case I can catch another problem.

This change has one downside :(, the ant target "test-tag" will fail which is 
correct in my eyes as this patch breaks the compatibility in a certain way. I 
do have some ideas to make is succeed but I did not include them in the patch.

> Refactor Searchable to not have RMI Remote dependency
> -----------------------------------------------------
>
>                 Key: LUCENE-1407
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1407
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Priority: Minor
>             Fix For: 2.9
>
>         Attachments: LUCENE-1407.patch
>
>
> Per http://lucene.markmail.org/message/fu34tuomnqejchfj?q=RemoteSearchable
> We should refactor Searchable slightly so that it doesn't extend the 
> java.rmi.Remote marker interface.  I believe the same could be achieved by 
> just marking the RemoteSearchable and refactoring the RMI implementation out 
> of core and into a contrib.
> If we do this, we should deprecate/denote it for 2.9 and then move it for 3.0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to