lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomoko Uchida (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LUCENE-2562) Make Luke a Lucene/Solr Module
Date Mon, 22 Oct 2018 13:52:00 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659008#comment-16659008
] 

Tomoko Uchida edited comment on LUCENE-2562 at 10/22/18 1:51 PM:
-----------------------------------------------------------------

Hi,

as we announced in the Lucene/Solr mailing lists, Luke was re-implemented on top of Swing.
[https://github.com/DmitryKey/luke|https://github.com/DmitryKey/luke]

The code is licensed under ALv2 and Swing is the part of JDK, so I think there is no obstacle
to make it a Lucene submodule.

I would like to create another patch and restart this issue, after just fixing styles and
colors.
The draft patch will be ready for review in the next few weeks or so but I am not sure about
when I should cut the feature branch for it. (Seems like Lucene 8.0 release workflow will
be kicked off soon.)
Can you please give me some advice?

Thanks.


was (Author: tomoko uchida):
Hi,

as we announced in the Lucene/Solr mailing lists, Luke was re-implemented on top of Swing.
[https://github.com/DmitryKey/luke|http://example.com]

The code is licensed under ALv2 and Swing is the part of JDK, so I think there is no obstacle
to make it a Lucene submodule.

I would like to create another patch and restart this issue, after just fixing styles and
colors.
The draft patch will be ready for review in the next few weeks or so but I am not sure about
when I should cut the feature branch for it. (Seems like Lucene 8.0 release workflow will
be kicked off soon.)
Can you please give me some advice?

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
>            Priority: Major
>              Labels: gsoc2014
>         Attachments: LUCENE-2562-Ivy.patch, LUCENE-2562-Ivy.patch, LUCENE-2562-Ivy.patch,
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, luke-javafx1.png, luke-javafx2.png, luke-javafx3.png,
luke1.jpg, luke2.jpg, luke3.jpg, lukeALE-documents.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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
(v7.6.3#76005)

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


Mime
View raw message