+1, but I don't have any time to contribute either.

On Thu, Mar 14, 2013 at 5:00 PM, Shai Erera (JIRA) <[email protected]> wrote:

>
>     [
> https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602728#comment-13602728]
>
> Shai Erera commented on LUCENE-2562:
> ------------------------------------
>
> Ah I missed that comment! indeed there's a version under sandbox/luke.
>
> > Make Luke a Lucene/Solr Module
> > ------------------------------
> >
> >                 Key: LUCENE-2562
> >                 URL: https://issues.apache.org/jira/browse/LUCENE-2562
> >             Project: Lucene - Core
> >          Issue Type: Task
> >            Reporter: Mark Miller
> >              Labels: gsoc2011, gsoc2012, lucene-gsoc-11, lucene-gsoc-12,
> mentor
> >         Attachments: luke1.jpg, luke2.jpg, luke3.jpg
> >
> >
> > see
> >
> http://search.lucidimagination.com/search/document/ee0e048c6b56ee2/luke_in_need_of_maintainer
> >
> http://search.lucidimagination.com/search/document/5e53136b7dcb609b/web_based_luke
> > I think it would be great if there was a version of Luke that always
> worked with trunk - and it would also be great if it was easier to match
> Luke jars with Lucene versions.
> > While I'd like to get GWT Luke into the mix as well, I think the easiest
> starting point is to straight port Luke to another UI toolkit before
> abstracting out DTO objects that both GWT Luke and Pivot Luke could share.
> > I've started slowly converting Luke's use of thinlet to Apache Pivot. I
> haven't/don't have a lot of time for this at the moment, but I've plugged
> away here and there over the past work or two. There is still a *lot* to do.
>
> --
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to