[
https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914864#action_12914864
]
Mark Miller commented on LUCENE-2562:
-------------------------------------
So, there is really a lot to do here - but I have gotten a fair amount done.
I'm near the point that I would like to share something - mostly so that I can
perhaps get some help doing more.
I think we can start the module well before this version of Luke can do
everything the current version of Luke can - but I'd like a spot to share
something that's not even really ready for a module spot. I'm looking for a
shared scratch pad to use to get to a rough module point.
Anyone mind if I make a spot in svn? lucene/luke, lucene/sandbox/luke or
something?
I'll pull any of the thinlet stuff out first. We may need to consider other
issues like code grants, but I think we can at least have a contained starting
point in svn before we get those details resolved? Thoughts? Otherwise I'll
need to share on an svn outside apache, which may cause the need for further
code grants issues, etc (developing outside of apache) that I'd rather just
avoid. But either way.
Also, if anyone is into translating, I'm working on localization from the
ground up, as well as modularizing and cleaning up a lot of the code. Luke in
German anyone?
> Make Luke a Lucene/Solr Module
> ------------------------------
>
> Key: LUCENE-2562
> URL: https://issues.apache.org/jira/browse/LUCENE-2562
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Mark Miller
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
