lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <>
Subject [jira] [Commented] (LUCENE-2562) Make Luke a Lucene/Solr Module
Date Mon, 22 Oct 2018 14:46:00 GMT


Steve Rowe commented on LUCENE-2562:

bq. as we announced in the Lucene/Solr mailing lists, Luke was re-implemented on top of Swing.

Wow, that was fast, congratulations!

bq. 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.


bq. 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.) Don't I have to care about the major version release procedure?

Once you put up a patch here I can commit it to the branch I already cut for this issue: {{jira/lucene-2562}}
(mentioned in a previous comment of mine on this issue).  Depending on when everything's wrapped
up, it may or may not make the 8.0 release; if not, then it will be part of whichever release
is upcoming.  So no, I don't think you need to worry about release procedures for this issue.
 Is there something specific you're concerned about?

> Make Luke a Lucene/Solr Module
> ------------------------------
>                 Key: LUCENE-2562
>                 URL:
>             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":
> "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 was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message