[
https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813296#comment-16813296
]
Uwe Schindler edited comment on LUCENE-2562 at 4/9/19 11:49 AM:
----------------------------------------------------------------
Hi [~Tomoko Uchida],
I prepared the branch to be squash-merged. Once you have your ASF account, I
would propose that you do the last step on your own. Here is the steps to do it:
- Checkout the branch from ASF gitbox (or use your own one from Github), does
not matter. Be sure to pull latest updates!!!
- Make sure to configure the GIT checkout to use your {{@apache) mail address
for commits (it's also wise to add it as an alias to github, so Github and ASF
bots can identify you as the same person). It may be wise to make the mail
address the default for all Lucene checkouts you maintain. Also it's wise to
have "origin" set to ASF gitbox and Github as alternative remote (e.g.,
"mocobeta")
- Switch back to master
- Run: {{git merge --squash jira/lucene-2562-luke-swing-3}}
- Commit the stuff with a useful commit message: {{git commit -m 'LUCENE-2562:
Add Luke as a Lucene module'}}
- Push changes
- Switch to branch "branch_8x" (the 8.x development branch)
- Cherry-pick the previous commit from master branch, or alternatively do the
same squashing merge.
- Push changes
Good luck - I am here for help.
Uwe
was (Author: thetaphi):
Hi [~Tomoko Uchida],
I prepared the branch to be squash-merged. Once you have your ASF account, I
would propose that you do the last step on your own. Here is the steps to do it:
- Checkout the branch from ASF gitbox (or use your own one from Github), does
not matter.
- Make sure to configure the GIT checkout to use your {{@apache) mail address
for commits (it's also wise to add it as an alias to github, so Github and ASF
bots can identify you as the same person). It may be wise to make the mail
address the default for all Lucene checkouts you maintain. Also it's wise to
have "origin" set to ASF gitbox and Github as alternative remote (e.g.,
"mocobeta")
- Switch back to master
- Run: {{git merge --squash jira/lucene-2562-luke-swing-3}}
- Commit the stuff with a useful commit message: {{git commit -m 'LUCENE-2562:
Add Luke as a Lucene module'}}
- Push changes
- Switch to branch "branch_8x" (the 8.x development branch)
- Cherry-pick the previous commit from master branch, or alternatively do the
same squashing merge.
- Push changes
Good luck - I am here for help.
Uwe
> 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
> Assignee: Tomoko Uchida
> 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, 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, screenshot-1.png, スクリーンショット 2018-11-05 9.19.47.png
>
> Time Spent: 50m
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
