[
https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292730#comment-14292730
]
Tomoko Uchida commented on LUCENE-2562:
---------------------------------------
Thanks everyone for all comments,
I recognize that the goal of this project is "making Luke a Lucene module".
I think it will be nice if there is a REST API server for Admin UIs, and have
some kind of pluggable architecture for external modules (like custom analyzers
provided by Solr, Elsticsearch, etc.)
But at first, I'd like to make it cover standalone Luke application features
under Apache license.
Dear Uwe and all,
> We already use IVY in Lucene/Solr. Please use the framework that is already
> there through common-build.xml / module-build.xml. It is enough to place
> ivy.xml in the module directory and make the module include the
> module-build.xml file.
I wanted to use the Lucene's framework, but currently, this module is placed
under
http://svn.apache.org/repos/asf/lucene/sandbox/ ,
not
http://svn.apache.org/repos/asf/lucene/dev/trunk
ivy.xml and ant tasks in my patch should be only temporary (for convenience in
development,) until this module will be merged to trunk.
So what can I do to smoothly integrate this module into Lucene trunk in the
future. If there are better ways, please let me know...
Thanks
> 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: gsoc2014
> Attachments: LUCENE-2562-ivy.patch, LUCENE-2562.patch,
> LUCENE-2562.patch, Luke-ALE-1.png, Luke-ALE-2.png, Luke-ALE-3.png,
> Luke-ALE-4.png, Luke-ALE-5.png, luke1.jpg, luke2.jpg, luke3.jpg
>
>
> see
> "RE: Luke - in need of maintainer":
> http://markmail.org/message/m4gsto7giltvrpuf
> "Web-based Luke": http://markmail.org/message/4xwps7p7ifltme5q
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
