You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2010/07/25 21:39:49 UTC
[jira] Created: (LUCENE-2562) Make Luke a Lucene/Solr Module
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
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [jira] Created: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by Mark Miller <ma...@gmail.com>.
Hey Pradeep,
At the moment, this is kind of a weekend project - last weekend I was
busy, and this weekend I'm headed to VT to see family - so I'm on a bit
of a break - but I'll be back to it.
I have not posted anything yet because I still need to separate out the
gpl thinlet stuff, but at the moment I find it very convenient to have
everything lumped together as I port. After I get a bit more done, I'll
work out a package with just the apache2 stuff and post what I have.
I may not get to all of the plug-ins and what not, but the majority of
the features left should not take too long to do.
- Mark
On 8/13/10 2:32 PM, Pradeep Pujari wrote:
> Hi All,
> Is it part of contrib now? Is it checked in somewhere either in Lucene or Solr?
> Thanks,
> Pradeep
>
> --- On Sun, 7/25/10, Mark Miller (JIRA) <ji...@apache.org> wrote:
>
>> From: Mark Miller (JIRA) <ji...@apache.org>
>> Subject: [jira] Created: (LUCENE-2562) Make Luke a Lucene/Solr Module
>> To: dev@lucene.apache.org
>> Date: Sunday, July 25, 2010, 12:39 PM
>> 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
>>
>>
>> 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: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [jira] Created: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by Pradeep Pujari <Pr...@rocketmail.com>.
Hi All,
Is it part of contrib now? Is it checked in somewhere either in Lucene or Solr?
Thanks,
Pradeep
--- On Sun, 7/25/10, Mark Miller (JIRA) <ji...@apache.org> wrote:
> From: Mark Miller (JIRA) <ji...@apache.org>
> Subject: [jira] Created: (LUCENE-2562) Make Luke a Lucene/Solr Module
> To: dev@lucene.apache.org
> Date: Sunday, July 25, 2010, 12:39 PM
> 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
>
>
> 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: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Simon Willnauer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916389#action_12916389 ]
Simon Willnauer commented on LUCENE-2562:
-----------------------------------------
{quote}
Would like to get going on pushing this in as a module - anyone want to comment on the legal aspect? Do we need a code grant or not? The original authors (AB and a couple plugin authors?) are committers, but the code was original developed outside Apache...
{quote}
I am not a legal expert but shooting an email to legal-discuss would bring clarification and we are on the safe side. Even if we would need one since all are around that should not be a big deal.
simon
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916450#action_12916450 ]
Grant Ingersoll commented on LUCENE-2562:
-----------------------------------------
How many contributors have there been to Luke outside of the ASF? I know Andrzej and Mark. I know I have put up a patch, I think. Was explicit permission given to use? I guess it comes down to ownership. I suppose you could split out where those patches were applied to, as well. Given that we are dropping the Thinlet stuff, anything that was changed there doesn't matter.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Andrzej Bialecki (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914873#action_12914873 ]
Andrzej Bialecki commented on LUCENE-2562:
-------------------------------------------
+1. I'm happy to do a code grant if people think it's necessary - after all, the non-thinlet parts are already licensed under ASL.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Simon Willnauer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914872#action_12914872 ]
Simon Willnauer commented on LUCENE-2562:
-----------------------------------------
bq. Anyone mind if I make a spot in svn? lucene/luke, lucene/sandbox/luke or something?
I just wonder why you don't branch and put it already in the right location. I think we should use branches more often though.
bq. 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?
Heh, sure I will do the German translation. - robert what about Thai :D
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916457#action_12916457 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
bq. shooting an email to legal-discuss
I'll go to legal discuss if I have to - but we have dealt with this type of thing before - so if the right people respond, I'd rather just go that route.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922414#action_12922414 ]
Robert Muir commented on LUCENE-2562:
-------------------------------------
{quote}
Still going - just kind of a weekend, nights project, of which I've been short of recently. Last weekend, 3 day hiking camping trip, previous 2 weekends before that (and all days in between) in Boston. Looking a little wavy going forward too, but I'm still heavily invested.
{quote}
Right, i meant really any legal issue/moving to trunk. Though maybe it doesnt have the complete feature set yet,
in trunk it would stay current and what you have so far is useful.
bq. Since unless someone says differently, I'm inclined to just move this (it's already in svn, so moving it under trunk is not much different).
+1
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916312#action_12916312 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
(P.S. Not to say this is that close to being done - would just like to get the legal stuff out of the way before spreading around too much in svn)
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909980#action_12909980 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
I haven't had any time to really work on this in a while, but I did bite the bullet and join the pivot mailing list and figured out my issues with making a fluid resizing layout - which is sweet and will hopefully motivate me to make some progress here soon.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914874#action_12914874 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
bq. I just wonder why you don't branch and put it already in the right location. I think we should use branches more often though
Because I really have no use/want for a branch of lucene/solr - luke is currently completely external to that, so what's the point really? When it's in module form, perhaps that would make more sense, but then I'm prob inclined to just put it in trunk and iterate.
bq. I'm happy to do a code grant if people think it's necessary - after all, the non-thinlet parts are already licensed under ASL.
I think the rule is that if it was developed outside of Apache, they want the grant, regardless of the license - especially for a codebase so large. I've heard different things when the dev is a committer - but they tend to err on the side of caution. We will see what Grant says.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892139#action_12892139 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
Re: Apache Pivot
So far its been a nice experience - the main draw back to it from my perspective is that it heavily favors fixed sized layouts. I really don't like this - I like fluid, resizing layouts. So far I haven't been able to make that happen, but its early yet - though it may be more difficult than worth it short term. For now I am just targeting a decent fixed size while the bulk of the grunt work is being done.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Updated: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated LUCENE-2562:
--------------------------------
Attachment: luke1.jpg
luke2.jpg
luke3.jpg
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Harwood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916452#action_12916452 ]
Mark Harwood commented on LUCENE-2562:
--------------------------------------
For the record, I'm obviously happy to grant any of my Luke contributions to Apache.
BTW - If anyone is looking at a revision of the GWT front end then this recent Google acquisition looks like it might be interesting: http://code.google.com/webtoolkit/tools/gwtdesigner/index.html
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914866#action_12914866 ]
Ryan McKinley commented on LUCENE-2562:
---------------------------------------
bq. Anyone mind if I make a spot in svn? lucene/luke, lucene/sandbox/luke or something?
+1 for lucene/sandbox/luke
We can always move it later
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914879#action_12914879 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
I've checked in the current state at: https://svn.apache.org/repos/asf/lucene/sandbox/luke
The main class is currently: org.apache.lucene.luke.ui.LukeApplication
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916308#action_12916308 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
I've taken Mark Harwood's cool Analyzers Tool plugin and ported it over as a first class citizen with it's own tab.
Great tool for checking out analysis - I'd hadn't really paid much attention to it till Robert pointed it out.
Check it out - I've got it in the latest jnlp at http://www.lucene-solr.com/luke.jnlp
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915070#action_12915070 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
If you just want to check out the current state of things, you can launch a jnlp version at http://www.lucene-solr.com/luke.jnlp
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916311#action_12916311 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
Would like to get going on pushing this in as a module - anyone want to comment on the legal aspect? Do we need a code grant or not? The original authors (AB and a couple plugin authors?) are committers, but the code was original developed outside Apache...
Anyone want to weigh in so we can move forward on module integration? Robert says he might lend a hand there.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Robert Muir (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922406#action_12922406 ]
Robert Muir commented on LUCENE-2562:
-------------------------------------
bq. I'll go to legal discuss if I have to - but we have dealt with this type of thing before - so if the right people respond, I'd rather just go that route.
What's happening with this one? It would be great to get it tied into the build in trunk.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922407#action_12922407 ]
Mark Miller commented on LUCENE-2562:
-------------------------------------
Still going - just kind of a weekend, nights project, of which I've been short of recently. Last weekend, 3 day hiking camping trip, previous 2 weekends before that (and all days in between) in Boston. Looking a little wavy going forward too, but I'm still heavily invested.
If Grant is not worried about getting a code grant, than neither am I. IMO, since the contributors are committers with CLA's, there is not much to worry about. Since unless someone says differently, I'm inclined to just move this (it's already in svn, so moving it under trunk is not much different).
If someone has a concern, we can hit legal-discuss though.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (LUCENE-2562) Make Luke a Lucene/Solr Module
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org