Re: [JENKINS] Lucene-Solr-8.x-Linux (32bit/jdk1.8.0_201) - Build # 1487 - Failure!
> ant clean clean-jars jar-checksums precommit I'll check, thanks Kevin. On Fri, Nov 15, 2019 at 3:53 AM Kevin Risden wrote: > > I get changed files on master after running the commands before precommit: > > ➜ lucene-solr git:(master) ✗ git status > On branch master > Your branch is up to date with 'origin/master'. > > Changes not staged for commit: > (use "git add/rm ..." to update what will be committed) > (use "git restore ..." to discard changes in working directory) > deleted: > solr/core/src/test-files/solr/question-answer-repository/question-answer-request-handler-1.0.jar > deleted: > solr/core/src/test-files/solr/question-answer-repository/question-answer-request-handler-1.1.jar > > no changes added to commit (use "git add" and/or "git commit -a") > > Kevin Risden > > > On Thu, Nov 14, 2019 at 5:21 PM Kevin Risden wrote: >> >> Ishan do you get an error with the following? >> >> ant clean clean-jars jar-checksums precommit >> >> This should regenerate any of the checksums. I haven't checked locally but >> might help. >> >> Kevin Risden >> >> >> On Thu, Nov 14, 2019 at 4:48 PM Ishan Chattopadhyaya >> wrote: >>> >>> No clue why licenses are being checked for those jars. Those are test >>> jars. I never got a precommit failure. >>> ALso, it seems licenses are not actually tested, but somehow those >>> sha1 files are generated but not cleaned up. Sigh! I think I have no >>> clue where to even start looking to solve this issue. >>> >>> On Fri, Nov 15, 2019 at 2:19 AM Policeman Jenkins Server >>> wrote: >>> > >>> > Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Linux/1487/ >>> > Java: 32bit/jdk1.8.0_201 -client -XX:+UseG1GC >>> > >>> > All tests passed >>> > >>> > Build Log: >>> > [...truncated 64469 lines...] >>> > BUILD FAILED >>> > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:634: The >>> > following error occurred while executing this line: >>> > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:507: The >>> > following error occurred while executing this line: >>> > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:494: Source >>> > checkout is dirty (unversioned/missing files) after running tests!!! >>> > Offending files: >>> > * solr/licenses/question-answer-request-handler-1.0.jar.sha1 >>> > * solr/licenses/question-answer-request-handler-1.1.jar.sha1 >>> > >>> > Total time: 129 minutes 26 seconds >>> > Build step 'Invoke Ant' marked build as failure >>> > Archiving artifacts >>> > Setting >>> > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >>> > [WARNINGS] Skipping publisher since build result is FAILURE >>> > Recording test results >>> > Setting >>> > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >>> > Email was triggered for: Failure - Any >>> > Sending email for trigger: Failure - Any >>> > Setting >>> > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >>> > Setting >>> > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >>> > Setting >>> > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >>> > Setting >>> > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >>> > Setting >>> > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >>> > Setting >>> > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >>> > >>> > - >>> > To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org >>> > For additional commands, e-mail: builds-h...@lucene.apache.org >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: [JENKINS] Lucene-Solr-8.x-Linux (32bit/jdk1.8.0_201) - Build # 1487 - Failure!
I get changed files on master after running the commands before precommit: ➜ lucene-solr git:(master) ✗ git status On branch master Your branch is up to date with 'origin/master'. Changes not staged for commit: (use "git add/rm ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) deleted: solr/core/src/test-files/solr/question-answer-repository/question-answer-request-handler-1.0.jar deleted: solr/core/src/test-files/solr/question-answer-repository/question-answer-request-handler-1.1.jar no changes added to commit (use "git add" and/or "git commit -a") Kevin Risden On Thu, Nov 14, 2019 at 5:21 PM Kevin Risden wrote: > Ishan do you get an error with the following? > > ant clean clean-jars jar-checksums precommit > > This should regenerate any of the checksums. I haven't checked locally but > might help. > > Kevin Risden > > > On Thu, Nov 14, 2019 at 4:48 PM Ishan Chattopadhyaya < > ichattopadhy...@gmail.com> wrote: > >> No clue why licenses are being checked for those jars. Those are test >> jars. I never got a precommit failure. >> ALso, it seems licenses are not actually tested, but somehow those >> sha1 files are generated but not cleaned up. Sigh! I think I have no >> clue where to even start looking to solve this issue. >> >> On Fri, Nov 15, 2019 at 2:19 AM Policeman Jenkins Server >> wrote: >> > >> > Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Linux/1487/ >> > Java: 32bit/jdk1.8.0_201 -client -XX:+UseG1GC >> > >> > All tests passed >> > >> > Build Log: >> > [...truncated 64469 lines...] >> > BUILD FAILED >> > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:634: The >> following error occurred while executing this line: >> > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:507: The >> following error occurred while executing this line: >> > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:494: Source >> checkout is dirty (unversioned/missing files) after running tests!!! >> Offending files: >> > * solr/licenses/question-answer-request-handler-1.0.jar.sha1 >> > * solr/licenses/question-answer-request-handler-1.1.jar.sha1 >> > >> > Total time: 129 minutes 26 seconds >> > Build step 'Invoke Ant' marked build as failure >> > Archiving artifacts >> > Setting >> ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >> > [WARNINGS] Skipping publisher since build result is FAILURE >> > Recording test results >> > Setting >> ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >> > Email was triggered for: Failure - Any >> > Sending email for trigger: Failure - Any >> > Setting >> ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >> > Setting >> ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >> > Setting >> ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >> > Setting >> ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >> > Setting >> ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >> > Setting >> ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 >> > >> > - >> > To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org >> > For additional commands, e-mail: builds-h...@lucene.apache.org >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >>
Re: [JENKINS] Lucene-Solr-8.x-Linux (32bit/jdk1.8.0_201) - Build # 1487 - Failure!
Ishan do you get an error with the following? ant clean clean-jars jar-checksums precommit This should regenerate any of the checksums. I haven't checked locally but might help. Kevin Risden On Thu, Nov 14, 2019 at 4:48 PM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > No clue why licenses are being checked for those jars. Those are test > jars. I never got a precommit failure. > ALso, it seems licenses are not actually tested, but somehow those > sha1 files are generated but not cleaned up. Sigh! I think I have no > clue where to even start looking to solve this issue. > > On Fri, Nov 15, 2019 at 2:19 AM Policeman Jenkins Server > wrote: > > > > Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Linux/1487/ > > Java: 32bit/jdk1.8.0_201 -client -XX:+UseG1GC > > > > All tests passed > > > > Build Log: > > [...truncated 64469 lines...] > > BUILD FAILED > > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:634: The > following error occurred while executing this line: > > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:507: The > following error occurred while executing this line: > > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:494: Source > checkout is dirty (unversioned/missing files) after running tests!!! > Offending files: > > * solr/licenses/question-answer-request-handler-1.0.jar.sha1 > > * solr/licenses/question-answer-request-handler-1.1.jar.sha1 > > > > Total time: 129 minutes 26 seconds > > Build step 'Invoke Ant' marked build as failure > > Archiving artifacts > > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > > [WARNINGS] Skipping publisher since build result is FAILURE > > Recording test results > > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > > Email was triggered for: Failure - Any > > Sending email for trigger: Failure - Any > > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > > > > - > > To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org > > For additional commands, e-mail: builds-h...@lucene.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
Re: Welcome Houston Putman as Lucene/Solr committer
Welcome Houston! On Thu, Nov 14, 2019 at 9:58 AM Anshum Gupta wrote: > > Hi all, > > Please join me in welcoming Houston Putman as the latest Lucene/Solr > committer! > > Houston has been involved with the community since 2013, when he first > contributed the Analytics contrib module. Since then he has been involved > with the community, participated in conferences and spoken about his work > with Lucene/Solr. In the recent past, he has been involved with getting Solr > to scale on Kubernetes. > > Looking forward to your commits to the Apache Lucene/Solr project :) > > Congratulations and welcome, Houston! It's a tradition to introduce yourself > with a brief bio. > > -- > Anshum Gupta -- Adrien - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: [JENKINS] Lucene-Solr-8.x-Linux (32bit/jdk1.8.0_201) - Build # 1487 - Failure!
No clue why licenses are being checked for those jars. Those are test jars. I never got a precommit failure. ALso, it seems licenses are not actually tested, but somehow those sha1 files are generated but not cleaned up. Sigh! I think I have no clue where to even start looking to solve this issue. On Fri, Nov 15, 2019 at 2:19 AM Policeman Jenkins Server wrote: > > Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Linux/1487/ > Java: 32bit/jdk1.8.0_201 -client -XX:+UseG1GC > > All tests passed > > Build Log: > [...truncated 64469 lines...] > BUILD FAILED > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:634: The following > error occurred while executing this line: > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:507: The following > error occurred while executing this line: > /home/jenkins/workspace/Lucene-Solr-8.x-Linux/build.xml:494: Source checkout > is dirty (unversioned/missing files) after running tests!!! Offending files: > * solr/licenses/question-answer-request-handler-1.0.jar.sha1 > * solr/licenses/question-answer-request-handler-1.1.jar.sha1 > > Total time: 129 minutes 26 seconds > Build step 'Invoke Ant' marked build as failure > Archiving artifacts > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > [WARNINGS] Skipping publisher since build result is FAILURE > Recording test results > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > Email was triggered for: Failure - Any > Sending email for trigger: Failure - Any > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > Setting > ANT_1_8_2_HOME=/home/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT_1.8.2 > > - > To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org > For additional commands, e-mail: builds-h...@lucene.apache.org - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Welcome Houston! On Thu, Nov 14, 2019 at 3:20 PM Yonik Seeley wrote: > Congrats Houston! > -Yonik > > On Thu, Nov 14, 2019 at 3:58 AM Anshum Gupta > wrote: > >> Hi all, >> >> Please join me in welcoming Houston Putman as the latest Lucene/Solr >> committer! >> >> Houston has been involved with the community since 2013, when he first >> contributed the Analytics contrib module. Since then he has been involved >> with the community, participated in conferences and spoken about his work >> with Lucene/Solr. In the recent past, he has been involved with getting >> Solr to scale on Kubernetes. >> >> Looking forward to your commits to the Apache Lucene/Solr project :) >> >> Congratulations and welcome, Houston! It's a tradition to introduce >> yourself with a brief bio. >> >> -- >> Anshum Gupta >> >
Re: Welcome Houston Putman as Lucene/Solr committer
Congrats Houston! -Yonik On Thu, Nov 14, 2019 at 3:58 AM Anshum Gupta wrote: > Hi all, > > Please join me in welcoming Houston Putman as the latest Lucene/Solr > committer! > > Houston has been involved with the community since 2013, when he first > contributed the Analytics contrib module. Since then he has been involved > with the community, participated in conferences and spoken about his work > with Lucene/Solr. In the recent past, he has been involved with getting > Solr to scale on Kubernetes. > > Looking forward to your commits to the Apache Lucene/Solr project :) > > Congratulations and welcome, Houston! It's a tradition to introduce > yourself with a brief bio. > > -- > Anshum Gupta >
Re: Welcome Houston Putman as Lucene/Solr committer
Thanks everyone! As requested, a brief history of me: A native Austinite, I went to The University of Texas at Austin. Back in 2013 I lucked into an internship with Bloomberg working on a new Search Infrastructure team. There I had my first exposure to Solr and built the first iteration of the Analytics Component. Since graduating in 2016, moving up to NYC and starting at Bloomberg full time, I have been working on Solr in various ways, from rewriting the Analytics Component to adding some features to various parts of SolrJ and fixing some weirdness in pivot facets. Lately I’ve been working (and presenting) on running Solr on Kubernetes. We’ve open sourced a Solr Kubernetes operator ( https://github.com/bloomberg/solr-operator), which is currently being developed with help from across the community. Our goal is to make this a standard and flexible way of running Solr in a cloud environment, which includes making Solr itself run better in the cloud. I can’t wait to continue working with y’all and making Solr as great as it can be! - Houston Putman On Thu, Nov 14, 2019 at 2:24 PM Varun Thacker wrote: > Congratulations and welcome Houston! > > On Thu, Nov 14, 2019 at 9:32 AM Tomás Fernández Löbbe < > tomasflo...@gmail.com> wrote: > >> Welcome Houston! >> >> On Thu, Nov 14, 2019 at 9:09 AM Kevin Risden wrote: >> >>> Congrats and welcome! >>> >>> Kevin Risden >>> >>> On Thu, Nov 14, 2019, 12:05 Jason Gerlowski >>> wrote: >>> Congratulations! On Thu, Nov 14, 2019 at 11:58 AM Gus Heck wrote: > > Congratulations and welcome :) > > On Thu, Nov 14, 2019 at 11:52 AM Namgyu Kim wrote: >> >> Congratulations and welcome, Houston! :D >> >> On Fri, Nov 15, 2019 at 1:18 AM Ken LaPorte wrote: >>> >>> Congratulations Houston! Well deserved honor. >>> >>> >>> >>> -- >>> Sent from: https://lucene.472066.n3.nabble.com/Lucene-Java-Developer-f564358.html >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> > > > -- > http://www.needhamsoftware.com (work) > http://www.the111shift.com (play) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Congratulations and welcome Houston! On Thu, Nov 14, 2019 at 9:32 AM Tomás Fernández Löbbe wrote: > Welcome Houston! > > On Thu, Nov 14, 2019 at 9:09 AM Kevin Risden wrote: > >> Congrats and welcome! >> >> Kevin Risden >> >> On Thu, Nov 14, 2019, 12:05 Jason Gerlowski >> wrote: >> >>> Congratulations! >>> >>> On Thu, Nov 14, 2019 at 11:58 AM Gus Heck wrote: >>> > >>> > Congratulations and welcome :) >>> > >>> > On Thu, Nov 14, 2019 at 11:52 AM Namgyu Kim wrote: >>> >> >>> >> Congratulations and welcome, Houston! :D >>> >> >>> >> On Fri, Nov 15, 2019 at 1:18 AM Ken LaPorte >>> wrote: >>> >>> >>> >>> Congratulations Houston! Well deserved honor. >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Sent from: >>> https://lucene.472066.n3.nabble.com/Lucene-Java-Developer-f564358.html >>> >>> >>> >>> - >>> >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>> >>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> >>> >>> > >>> > >>> > -- >>> > http://www.needhamsoftware.com (work) >>> > http://www.the111shift.com (play) >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> >>>
Re: gradle module/project structure
Want to raise a JIRA (task?) and put it in the umbrella task? (SOLR-13914)? I’m trying to keep all these kinds of TODO’s in a place we won’t forget them. Up to you… > On Nov 14, 2019, at 11:56 AM, Dawid Weiss wrote: > >> I didn't realize you could specify a folder name with -p ! I think >> that covers the use case I was describing. If the module names we have >> are helpful in an IDE, that's reason enough to keep them >> fully-qualified. > > I would opt to change them to reflect folder structure precisely (it's > simpler to reason about them then) but it'll have to wait until ant is > gone. > > Dawid > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: [JENKINS] Lucene-Solr-master-Linux (64bit/jdk-13) - Build # 25021 - Failure!
I'll take a look. It was because of SOLR-13662, which passed many,
many tests locally.
On Thu, Nov 14, 2019 at 10:41 PM Policeman Jenkins Server
wrote:
>
> Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/25021/
> Java: 64bit/jdk-13 -XX:+UseCompressedOops -XX:+UseSerialGC
>
> 1 tests failed.
> FAILED: org.apache.solr.cloud.PackageManagerCLITest.testPackageManager
>
> Error Message:
> Could not get expected value '1.1.0' for path
> 'config/requestHandler/\/mypath2/_packageinfo_/version' full output: {
> "responseHeader":{ "status":0, "QTime":0},
> "config":{"requestHandler":{"/mypath2":{ "name":"/mypath2",
> "class":"question-answer:fullstory.QARequestHandler",
> "_packageinfo_":{ "package":"question-answer",
> "version":"1.0.0",
> "files":["/package/question-answer/1.0.0/question-answer-request-handler-1.0.jar"],
>"manifest":"/package/question-answer/1.0.0/manifest.json",
>
> "manifestSHA512":"a91ab5a2c5abd53f0f72c256592c2be8b667cecb8226ac054aeed4d28aac9d743311442f2d58539bb83663a19bd1efb310aaadfd77bea458f3d475161721a114"},
> from server: https://127.0.0.1:45931/solr/abc
>
> Stack Trace:
> java.lang.AssertionError: Could not get expected value '1.1.0' for path
> 'config/requestHandler/\/mypath2/_packageinfo_/version' full output: {
> "responseHeader":{
> "status":0,
> "QTime":0},
> "config":{"requestHandler":{"/mypath2":{
> "name":"/mypath2",
> "class":"question-answer:fullstory.QARequestHandler",
> "_packageinfo_":{
> "package":"question-answer",
> "version":"1.0.0",
>
> "files":["/package/question-answer/1.0.0/question-answer-request-handler-1.0.jar"],
> "manifest":"/package/question-answer/1.0.0/manifest.json",
>
> "manifestSHA512":"a91ab5a2c5abd53f0f72c256592c2be8b667cecb8226ac054aeed4d28aac9d743311442f2d58539bb83663a19bd1efb310aaadfd77bea458f3d475161721a114"},
> from server: https://127.0.0.1:45931/solr/abc
> at
> __randomizedtesting.SeedInfo.seed([7FB7A8609119800:45131E80BFF47AB]:0)
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> org.apache.solr.core.TestSolrConfigHandler.testForResponseElement(TestSolrConfigHandler.java:590)
> at
> org.apache.solr.cloud.PackageManagerCLITest.assertPackageVersion(PackageManagerCLITest.java:149)
> at
> org.apache.solr.cloud.PackageManagerCLITest.testPackageManager(PackageManagerCLITest.java:129)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:567)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1750)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:938)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:974)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:988)
> at
> com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
> at
> org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:49)
> at
> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
> at
> org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:48)
> at
> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
> at
> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:368)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:817)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:468)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:947)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:832)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:883)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:894)
> at
Re: Welcome Houston Putman as Lucene/Solr committer
Welcome Houston! On Thu, Nov 14, 2019 at 9:09 AM Kevin Risden wrote: > Congrats and welcome! > > Kevin Risden > > On Thu, Nov 14, 2019, 12:05 Jason Gerlowski wrote: > >> Congratulations! >> >> On Thu, Nov 14, 2019 at 11:58 AM Gus Heck wrote: >> > >> > Congratulations and welcome :) >> > >> > On Thu, Nov 14, 2019 at 11:52 AM Namgyu Kim wrote: >> >> >> >> Congratulations and welcome, Houston! :D >> >> >> >> On Fri, Nov 15, 2019 at 1:18 AM Ken LaPorte >> wrote: >> >>> >> >>> Congratulations Houston! Well deserved honor. >> >>> >> >>> >> >>> >> >>> -- >> >>> Sent from: >> https://lucene.472066.n3.nabble.com/Lucene-Java-Developer-f564358.html >> >>> >> >>> - >> >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> >>> For additional commands, e-mail: dev-h...@lucene.apache.org >> >>> >> > >> > >> > -- >> > http://www.needhamsoftware.com (work) >> > http://www.the111shift.com (play) >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >>
Re: Welcome Houston Putman as Lucene/Solr committer
Congrats and welcome! Kevin Risden On Thu, Nov 14, 2019, 12:05 Jason Gerlowski wrote: > Congratulations! > > On Thu, Nov 14, 2019 at 11:58 AM Gus Heck wrote: > > > > Congratulations and welcome :) > > > > On Thu, Nov 14, 2019 at 11:52 AM Namgyu Kim wrote: > >> > >> Congratulations and welcome, Houston! :D > >> > >> On Fri, Nov 15, 2019 at 1:18 AM Ken LaPorte > wrote: > >>> > >>> Congratulations Houston! Well deserved honor. > >>> > >>> > >>> > >>> -- > >>> Sent from: > https://lucene.472066.n3.nabble.com/Lucene-Java-Developer-f564358.html > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > >>> For additional commands, e-mail: dev-h...@lucene.apache.org > >>> > > > > > > -- > > http://www.needhamsoftware.com (work) > > http://www.the111shift.com (play) > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
Re: Welcome Houston Putman as Lucene/Solr committer
Congratulations! On Thu, Nov 14, 2019 at 11:58 AM Gus Heck wrote: > > Congratulations and welcome :) > > On Thu, Nov 14, 2019 at 11:52 AM Namgyu Kim wrote: >> >> Congratulations and welcome, Houston! :D >> >> On Fri, Nov 15, 2019 at 1:18 AM Ken LaPorte wrote: >>> >>> Congratulations Houston! Well deserved honor. >>> >>> >>> >>> -- >>> Sent from: >>> https://lucene.472066.n3.nabble.com/Lucene-Java-Developer-f564358.html >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> > > > -- > http://www.needhamsoftware.com (work) > http://www.the111shift.com (play) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Congratulations and welcome :) On Thu, Nov 14, 2019 at 11:52 AM Namgyu Kim wrote: > Congratulations and welcome, Houston! :D > > On Fri, Nov 15, 2019 at 1:18 AM Ken LaPorte wrote: > >> Congratulations Houston! Well deserved honor. >> >> >> >> -- >> Sent from: >> https://lucene.472066.n3.nabble.com/Lucene-Java-Developer-f564358.html >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >> -- http://www.needhamsoftware.com (work) http://www.the111shift.com (play)
Re: gradle module/project structure
> I didn't realize you could specify a folder name with -p ! I think > that covers the use case I was describing. If the module names we have > are helpful in an IDE, that's reason enough to keep them > fully-qualified. I would opt to change them to reflect folder structure precisely (it's simpler to reason about them then) but it'll have to wait until ant is gone. Dawid - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Congratulations and welcome, Houston! :D On Fri, Nov 15, 2019 at 1:18 AM Ken LaPorte wrote: > Congratulations Houston! Well deserved honor. > > > > -- > Sent from: > https://lucene.472066.n3.nabble.com/Lucene-Java-Developer-f564358.html > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
Re: gradle module/project structure
I didn't realize you could specify a folder name with -p ! I think that covers the use case I was describing. If the module names we have are helpful in an IDE, that's reason enough to keep them fully-qualified. On Thu, Nov 14, 2019 at 11:13 AM Dawid Weiss wrote: > > Perhaps. I don't use this wrapper. Knowing the difference and > understanding what you're expressing with both variants is all it > takes, really. > > D. > > On Thu, Nov 14, 2019 at 5:08 PM Jan Høydahl wrote: > > > > Isn’t this why Mark recommended using gdub (gw) so you can run from within > > sub folders? > > > > Jan Høydahl > > > > > 14. nov. 2019 kl. 14:22 skrev Dawid Weiss : > > > > > > Your understanding is incorrect, Michael. > > > > > > This: > > > > > >> ./gradlew lucene:lucene-analyzers:lucene-analyzers-nori:test seems to > > >> work > > > > > > runs task 'test' inside module > > > lucene:lucene-analyzers:lucene-analyzers-nori > > > > > > while this: > > > > > >> ./gradlew lucene:lucene-analyzers:test > > > > > > tries to run task 'test' in module lucene:lucene-analyzers but this > > > project doesn't have this task at all. > > > > > > Try pointing at a folder instead of fully qualified project name > > > (benefit of the shell expanding paths as well): > > > > > > ./gradlew -p lucene/analysis test > > > > > > the difference being it'll try to run the 'test' task in any of the > > > submodules under that folder. > > > > > > Also, this will show you all available tasks and projects: > > > > > > gradlew tasks --all > > > > > > > > > Dawid > > > > > >> > > >> does not. it would really be nice to have a way to run all the analysis > > >> tests > > >> > > >>> On Thu, Nov 14, 2019 at 8:05 AM Michael Sokolov > > >>> wrote: > > >>> > > >>> I'm trying to run the tests in the lucene/analysis module (really I'd > > >>> like to run tests in lucene/analysis/kuromoji), but I'm having trouble > > >>> figuring out the naming convention and/or the project structure. It > > >>> doesn't seem to be the same as the directory structure? EG I am able > > >>> to run tests in core with: > > >>> > > >>>./gradlew lucene:lucene-core:test > > >>> > > >>> although I expected it to be > > >>> > > >>>./gradlew lucene:core:test > > >>> > > >>> I forget how I stumbled on the "correct" naming > > >>> > > >>> but none of these work: > > >>> > > >>>./gradlew lucene:analysis:test > > >>>./gradlew lucene:lucene-analysis:test > > >>>./gradlew lucene:analyzers:test > > >>>./gradlew lucene:lucene-analyzers:test > > >>> > > >>> (gradle suggested the "lucene-analyzers" project name) > > >>> > > >>> where is the mapping from module to gradle project name kept? Can we > > >>> make it consistent with the directory naming, and ideally not have an > > >>> explicit mapping at all? > > >> > > >> - > > >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > >> For additional commands, e-mail: dev-h...@lucene.apache.org > > >> > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > > For additional commands, e-mail: dev-h...@lucene.apache.org > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Congratulations Houston! Well deserved honor. -- Sent from: https://lucene.472066.n3.nabble.com/Lucene-Java-Developer-f564358.html - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: gradle module/project structure
Perhaps. I don't use this wrapper. Knowing the difference and understanding what you're expressing with both variants is all it takes, really. D. On Thu, Nov 14, 2019 at 5:08 PM Jan Høydahl wrote: > > Isn’t this why Mark recommended using gdub (gw) so you can run from within > sub folders? > > Jan Høydahl > > > 14. nov. 2019 kl. 14:22 skrev Dawid Weiss : > > > > Your understanding is incorrect, Michael. > > > > This: > > > >> ./gradlew lucene:lucene-analyzers:lucene-analyzers-nori:test seems to work > > > > runs task 'test' inside module lucene:lucene-analyzers:lucene-analyzers-nori > > > > while this: > > > >> ./gradlew lucene:lucene-analyzers:test > > > > tries to run task 'test' in module lucene:lucene-analyzers but this > > project doesn't have this task at all. > > > > Try pointing at a folder instead of fully qualified project name > > (benefit of the shell expanding paths as well): > > > > ./gradlew -p lucene/analysis test > > > > the difference being it'll try to run the 'test' task in any of the > > submodules under that folder. > > > > Also, this will show you all available tasks and projects: > > > > gradlew tasks --all > > > > > > Dawid > > > >> > >> does not. it would really be nice to have a way to run all the analysis > >> tests > >> > >>> On Thu, Nov 14, 2019 at 8:05 AM Michael Sokolov > >>> wrote: > >>> > >>> I'm trying to run the tests in the lucene/analysis module (really I'd > >>> like to run tests in lucene/analysis/kuromoji), but I'm having trouble > >>> figuring out the naming convention and/or the project structure. It > >>> doesn't seem to be the same as the directory structure? EG I am able > >>> to run tests in core with: > >>> > >>>./gradlew lucene:lucene-core:test > >>> > >>> although I expected it to be > >>> > >>>./gradlew lucene:core:test > >>> > >>> I forget how I stumbled on the "correct" naming > >>> > >>> but none of these work: > >>> > >>>./gradlew lucene:analysis:test > >>>./gradlew lucene:lucene-analysis:test > >>>./gradlew lucene:analyzers:test > >>>./gradlew lucene:lucene-analyzers:test > >>> > >>> (gradle suggested the "lucene-analyzers" project name) > >>> > >>> where is the mapping from module to gradle project name kept? Can we > >>> make it consistent with the directory naming, and ideally not have an > >>> explicit mapping at all? > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > >> For additional commands, e-mail: dev-h...@lucene.apache.org > >> > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: gradle module/project structure
Isn’t this why Mark recommended using gdub (gw) so you can run from within sub folders? Jan Høydahl > 14. nov. 2019 kl. 14:22 skrev Dawid Weiss : > > Your understanding is incorrect, Michael. > > This: > >> ./gradlew lucene:lucene-analyzers:lucene-analyzers-nori:test seems to work > > runs task 'test' inside module lucene:lucene-analyzers:lucene-analyzers-nori > > while this: > >> ./gradlew lucene:lucene-analyzers:test > > tries to run task 'test' in module lucene:lucene-analyzers but this > project doesn't have this task at all. > > Try pointing at a folder instead of fully qualified project name > (benefit of the shell expanding paths as well): > > ./gradlew -p lucene/analysis test > > the difference being it'll try to run the 'test' task in any of the > submodules under that folder. > > Also, this will show you all available tasks and projects: > > gradlew tasks --all > > > Dawid > >> >> does not. it would really be nice to have a way to run all the analysis tests >> >>> On Thu, Nov 14, 2019 at 8:05 AM Michael Sokolov wrote: >>> >>> I'm trying to run the tests in the lucene/analysis module (really I'd >>> like to run tests in lucene/analysis/kuromoji), but I'm having trouble >>> figuring out the naming convention and/or the project structure. It >>> doesn't seem to be the same as the directory structure? EG I am able >>> to run tests in core with: >>> >>>./gradlew lucene:lucene-core:test >>> >>> although I expected it to be >>> >>>./gradlew lucene:core:test >>> >>> I forget how I stumbled on the "correct" naming >>> >>> but none of these work: >>> >>>./gradlew lucene:analysis:test >>>./gradlew lucene:lucene-analysis:test >>>./gradlew lucene:analyzers:test >>>./gradlew lucene:lucene-analyzers:test >>> >>> (gradle suggested the "lucene-analyzers" project name) >>> >>> where is the mapping from module to gradle project name kept? Can we >>> make it consistent with the directory naming, and ideally not have an >>> explicit mapping at all? >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Congrats and welcome Houston! Regards, Munendra S N On Thu, Nov 14, 2019 at 6:51 PM Karl Wright wrote: > Welcome! > Karl > > On Thu, Nov 14, 2019 at 8:17 AM Michael Sokolov > wrote: > >> Hi Houston, welcome! >> >> On Thu, Nov 14, 2019 at 7:23 AM Erick Erickson >> wrote: >> > >> > Welcome! >> > >> > > On Nov 14, 2019, at 5:19 AM, Jan Høydahl >> wrote: >> > > >> > > Congrats and welcome Houston! >> > > >> > > -- >> > > Jan Høydahl, search solution architect >> > > Cominvent AS - www.cominvent.com >> > > >> > >> 14. nov. 2019 kl. 09:57 skrev Anshum Gupta : >> > >> >> > >> Hi all, >> > >> >> > >> Please join me in welcoming Houston Putman as the latest Lucene/Solr >> committer! >> > >> >> > >> Houston has been involved with the community since 2013, when he >> first contributed the Analytics contrib module. Since then he has been >> involved with the community, participated in conferences and spoken about >> his work with Lucene/Solr. In the recent past, he has been involved with >> getting Solr to scale on Kubernetes. >> > >> >> > >> Looking forward to your commits to the Apache Lucene/Solr project :) >> > >> >> > >> Congratulations and welcome, Houston! It's a tradition to introduce >> yourself with a brief bio. >> > >> >> > >> -- >> > >> Anshum Gupta >> > > >> > >> > >> > - >> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> > For additional commands, e-mail: dev-h...@lucene.apache.org >> > >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >>
Re: gradle module/project structure
Your understanding is incorrect, Michael. This: > ./gradlew lucene:lucene-analyzers:lucene-analyzers-nori:test seems to work runs task 'test' inside module lucene:lucene-analyzers:lucene-analyzers-nori while this: > ./gradlew lucene:lucene-analyzers:test tries to run task 'test' in module lucene:lucene-analyzers but this project doesn't have this task at all. Try pointing at a folder instead of fully qualified project name (benefit of the shell expanding paths as well): ./gradlew -p lucene/analysis test the difference being it'll try to run the 'test' task in any of the submodules under that folder. Also, this will show you all available tasks and projects: gradlew tasks --all Dawid > > does not. it would really be nice to have a way to run all the analysis tests > > On Thu, Nov 14, 2019 at 8:05 AM Michael Sokolov wrote: > > > > I'm trying to run the tests in the lucene/analysis module (really I'd > > like to run tests in lucene/analysis/kuromoji), but I'm having trouble > > figuring out the naming convention and/or the project structure. It > > doesn't seem to be the same as the directory structure? EG I am able > > to run tests in core with: > > > > ./gradlew lucene:lucene-core:test > > > > although I expected it to be > > > > ./gradlew lucene:core:test > > > > I forget how I stumbled on the "correct" naming > > > > but none of these work: > > > > ./gradlew lucene:analysis:test > > ./gradlew lucene:lucene-analysis:test > > ./gradlew lucene:analyzers:test > > ./gradlew lucene:lucene-analyzers:test > > > > (gradle suggested the "lucene-analyzers" project name) > > > > where is the mapping from module to gradle project name kept? Can we > > make it consistent with the directory naming, and ideally not have an > > explicit mapping at all? > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Welcome! Karl On Thu, Nov 14, 2019 at 8:17 AM Michael Sokolov wrote: > Hi Houston, welcome! > > On Thu, Nov 14, 2019 at 7:23 AM Erick Erickson > wrote: > > > > Welcome! > > > > > On Nov 14, 2019, at 5:19 AM, Jan Høydahl > wrote: > > > > > > Congrats and welcome Houston! > > > > > > -- > > > Jan Høydahl, search solution architect > > > Cominvent AS - www.cominvent.com > > > > > >> 14. nov. 2019 kl. 09:57 skrev Anshum Gupta : > > >> > > >> Hi all, > > >> > > >> Please join me in welcoming Houston Putman as the latest Lucene/Solr > committer! > > >> > > >> Houston has been involved with the community since 2013, when he > first contributed the Analytics contrib module. Since then he has been > involved with the community, participated in conferences and spoken about > his work with Lucene/Solr. In the recent past, he has been involved with > getting Solr to scale on Kubernetes. > > >> > > >> Looking forward to your commits to the Apache Lucene/Solr project :) > > >> > > >> Congratulations and welcome, Houston! It's a tradition to introduce > yourself with a brief bio. > > >> > > >> -- > > >> Anshum Gupta > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
Re: Welcome Houston Putman as Lucene/Solr committer
Hi Houston, welcome! On Thu, Nov 14, 2019 at 7:23 AM Erick Erickson wrote: > > Welcome! > > > On Nov 14, 2019, at 5:19 AM, Jan Høydahl wrote: > > > > Congrats and welcome Houston! > > > > -- > > Jan Høydahl, search solution architect > > Cominvent AS - www.cominvent.com > > > >> 14. nov. 2019 kl. 09:57 skrev Anshum Gupta : > >> > >> Hi all, > >> > >> Please join me in welcoming Houston Putman as the latest Lucene/Solr > >> committer! > >> > >> Houston has been involved with the community since 2013, when he first > >> contributed the Analytics contrib module. Since then he has been involved > >> with the community, participated in conferences and spoken about his work > >> with Lucene/Solr. In the recent past, he has been involved with getting > >> Solr to scale on Kubernetes. > >> > >> Looking forward to your commits to the Apache Lucene/Solr project :) > >> > >> Congratulations and welcome, Houston! It's a tradition to introduce > >> yourself with a brief bio. > >> > >> -- > >> Anshum Gupta > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: gradle module/project structure
OK with some grepping I I found these module names in various places (looks like they were defined as maven module names, where I guess maybe it is best practice for every submodule's name to contain the complete hierarchy of all its ancestor modules??) ./gradlew lucene:lucene-analyzers:lucene-analyzers-nori:test seems to work but ./gradlew lucene:lucene-analyzers:test does not. it would really be nice to have a way to run all the analysis tests On Thu, Nov 14, 2019 at 8:05 AM Michael Sokolov wrote: > > I'm trying to run the tests in the lucene/analysis module (really I'd > like to run tests in lucene/analysis/kuromoji), but I'm having trouble > figuring out the naming convention and/or the project structure. It > doesn't seem to be the same as the directory structure? EG I am able > to run tests in core with: > > ./gradlew lucene:lucene-core:test > > although I expected it to be > > ./gradlew lucene:core:test > > I forget how I stumbled on the "correct" naming > > but none of these work: > > ./gradlew lucene:analysis:test > ./gradlew lucene:lucene-analysis:test > ./gradlew lucene:analyzers:test > ./gradlew lucene:lucene-analyzers:test > > (gradle suggested the "lucene-analyzers" project name) > > where is the mapping from module to gradle project name kept? Can we > make it consistent with the directory naming, and ideally not have an > explicit mapping at all? - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
gradle module/project structure
I'm trying to run the tests in the lucene/analysis module (really I'd like to run tests in lucene/analysis/kuromoji), but I'm having trouble figuring out the naming convention and/or the project structure. It doesn't seem to be the same as the directory structure? EG I am able to run tests in core with: ./gradlew lucene:lucene-core:test although I expected it to be ./gradlew lucene:core:test I forget how I stumbled on the "correct" naming but none of these work: ./gradlew lucene:analysis:test ./gradlew lucene:lucene-analysis:test ./gradlew lucene:analyzers:test ./gradlew lucene:lucene-analyzers:test (gradle suggested the "lucene-analyzers" project name) where is the mapping from module to gradle project name kept? Can we make it consistent with the directory naming, and ideally not have an explicit mapping at all? - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Welcome! > On Nov 14, 2019, at 5:19 AM, Jan Høydahl wrote: > > Congrats and welcome Houston! > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > >> 14. nov. 2019 kl. 09:57 skrev Anshum Gupta : >> >> Hi all, >> >> Please join me in welcoming Houston Putman as the latest Lucene/Solr >> committer! >> >> Houston has been involved with the community since 2013, when he first >> contributed the Analytics contrib module. Since then he has been involved >> with the community, participated in conferences and spoken about his work >> with Lucene/Solr. In the recent past, he has been involved with getting Solr >> to scale on Kubernetes. >> >> Looking forward to your commits to the Apache Lucene/Solr project :) >> >> Congratulations and welcome, Houston! It's a tradition to introduce yourself >> with a brief bio. >> >> -- >> Anshum Gupta > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Congrats and welcome Houston!! On Thu, 14 Nov 2019 at 11:54, David Smiley wrote: > Congrats Houston! Woohoo! > > On Thu, Nov 14, 2019 at 3:58 AM Anshum Gupta > wrote: > >> Hi all, >> >> Please join me in welcoming Houston Putman as the latest Lucene/Solr >> committer! >> >> Houston has been involved with the community since 2013, when he first >> contributed the Analytics contrib module. Since then he has been involved >> with the community, participated in conferences and spoken about his work >> with Lucene/Solr. In the recent past, he has been involved with getting >> Solr to scale on Kubernetes. >> >> Looking forward to your commits to the Apache Lucene/Solr project :) >> >> Congratulations and welcome, Houston! It's a tradition to introduce >> yourself with a brief bio. >> >> -- >> Anshum Gupta >> > -- > Sent from Gmail Mobile > -- *Best regards,* *Cao Mạnh Đạt* *E-mail: caomanhdat...@gmail.com *
Re: Welcome Houston Putman as Lucene/Solr committer
Congrats Houston! Woohoo! On Thu, Nov 14, 2019 at 3:58 AM Anshum Gupta wrote: > Hi all, > > Please join me in welcoming Houston Putman as the latest Lucene/Solr > committer! > > Houston has been involved with the community since 2013, when he first > contributed the Analytics contrib module. Since then he has been involved > with the community, participated in conferences and spoken about his work > with Lucene/Solr. In the recent past, he has been involved with getting > Solr to scale on Kubernetes. > > Looking forward to your commits to the Apache Lucene/Solr project :) > > Congratulations and welcome, Houston! It's a tradition to introduce > yourself with a brief bio. > > -- > Anshum Gupta > -- Sent from Gmail Mobile
Check out the new Website built by Pelican from git repo
Hi all, In https://issues.apache.org/jira/browse/LUCENE-8987 we move the website from CMS (svn/forrest) to a git repo, auto built by Pelican by pushing to master branch. We just got the first staging build working and pushed to https://lucene.staged.apache.org/ Please take a look and report back findings, so we can tighten it up before replacing the production site with this one. There are a few known limitations * JavaDoc missing (LUCENE-9014) * RefGuide missing (LUCENE-9020) * Solr Resource page lacks some content (LUCENE-9048) If you want to lend a helping hand to land the remaining pieces, please do! -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Welcome Houston Putman as Lucene/Solr committer
Congrats and welcome Houston! -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 14. nov. 2019 kl. 09:57 skrev Anshum Gupta : > > Hi all, > > Please join me in welcoming Houston Putman as the latest Lucene/Solr > committer! > > Houston has been involved with the community since 2013, when he first > contributed the Analytics contrib module. Since then he has been involved > with the community, participated in conferences and spoken about his work > with Lucene/Solr. In the recent past, he has been involved with getting Solr > to scale on Kubernetes. > > Looking forward to your commits to the Apache Lucene/Solr project :) > > Congratulations and welcome, Houston! It's a tradition to introduce yourself > with a brief bio. > > -- > Anshum Gupta
Re: Solr Gradle build (SOLR-13452)
> org.asciidoctor:asciidoctorj=1.6.0-alpha.5
>
> with
>
> org.asciidoctor:asciidoctor-ant=1.6.2
> org.asciidoctor:asciidoctorj=1.6.2
You don't need to add asciidoctor-ant - it isn't used anywhere as an
explicit dependency.
> If I remove one or both, and try “gw jarChecksums” Bad Things Happen.
If you remove the "org.asciidoctor:asciidoctorj" then indeed the
dependency in solr-ref-guide/build.gradle won't be resolvable -- this
one:
tools('org.asciidoctor:asciidoctorj')
the other line is not required. I checked gw jarChecksums and
everything works fine.
> Whether that’s because I have something polluted in my env is an open
> question.
Maybe. That's why I asked for the debug log.
Jar checksums work for Lucene for me now.
.\gradlew -p lucene checkLicenses --rerun-tasks
although the content of those folders differs for gradle and ant
(gradle has morfologik-fsa-2.1.6.jar.sha1 while ant has
morfologik-fsa-2.1.5.jar.sha1, for example).
Jar checksums for Solr don't work:
.\gradlew -p solr checkLicenses --rerun-tasks
this is because
1) the task that resolves them in gradle collects dependencies from
all configurations, regardless of whether they're used internally at
build time or truly exported at runtime. In ant we don't have (or
verify) all of these JARs. I don't know if we must (or should). An
example is the jruby dependency used for compiling the refguide. We
could add sha files, licenses, etc. to all of these but it'll be a
pain to upgrade anything after that:
Scanned 321 JAR file(s) for licenses (in 1.09s.), 129 error(s).
2) some exclusions of transitive dependencies would be required in the
gradle build to match ant's configs.
Dawid
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
Welcome Houston Putman as Lucene/Solr committer
Hi all, Please join me in welcoming Houston Putman as the latest Lucene/Solr committer! Houston has been involved with the community since 2013, when he first contributed the Analytics contrib module. Since then he has been involved with the community, participated in conferences and spoken about his work with Lucene/Solr. In the recent past, he has been involved with getting Solr to scale on Kubernetes. Looking forward to your commits to the Apache Lucene/Solr project :) Congratulations and welcome, Houston! It's a tradition to introduce yourself with a brief bio. -- Anshum Gupta
Re: Do we want to pursue an LTS designation?
I agree with the removal of LTS designation - there’s no formal commitment from the community to support this or that release for that long. Even though in practice bug fixes are often backported to older branches that are still widely used, there’s no actual contract to do so, and implying there is one is misleading. > On 13 Nov 2019, at 22:46, Chris Hostetter wrote: > > > : The term LTS is used loosely and we actually do not promise anything. What > we say is > : > : > 7.7.x Version in the previous major release for bugfixes only (LTS) > ... > > : Being the one coining the LTS phrasing I am not opposed to changing it > : to something else. But through the years we have used that term I have > : not seen a lot of such requests. > > I didn't realize you had put that up on the site -- it does seem very > missleading to me as the "LT" in "LTS" is suppose to mean "Long Term" but > we do not -- in practice or intent -- have any plans as a project to > support "7.7.x" in particular any longer then we would any other arbitrary > "latest" minor release. > > Nor did we ever give users who initially installed 7.7.0 when it came out > any reason to think it would be "supported" (and get bug fixes) for a > "longer term" then a hypothetical 7.8.0 that might have come out a day > after they installed some 7.7.x, and replace it's row on that page that > you've labeled "LTS". > > We may not have ever gotten questions about it, but that may just be > because people have very specific assumptions about what it means, and > never thought to ask questions to verify those assumptions. > > I think, given how the project *actually* supports releases, I think we > should remove references to "LTS" from that page, and leave the other > description "Version in the previous major release for bugfixes only" as > it stands -- or perhaps tighten it up even more: "Version in the previous > major release that may get bug fixs" > > > -Hoss > http://www.lucidworks.com/ > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Solr Gradle build (SOLR-13452)
Sorry, I am just looking at this now and about to call it a night soon.
I'll try and get to it tomorrow/todayi.e Friday but if you get to it before
I do, please move forward.
On Wed, Nov 13, 2019 at 4:26 PM Erick Erickson
wrote:
> Anshum et. al. :
>
> It’s been a busy day, never got back to it. I’ll try to push my changes,
> mostly updating the dependencies tonight.
>
> It’s not ready to merge into master yet, there’s this problem:
>
> ant -Dtestcase=TestKoreanTokenizer test
>
> fails with:
>
> java.lang.RuntimeException: Cannot find userdict.txt in test classpath!
>
> userdict.txt gets copied when I test on the trunk branch to (at least I
> think this is the corresponding one):
>
>
> ./lucene/build/analysis/nori/classes/test/org/apache/lucene/analysis/ko/userdict.txt
>
> So my presumption is that the ant build takes care of this and somehow the
> classpath is set to include it.
>
> This is on a clean checkout of the current gradle_8 branch, _without_
> trying to do anything with Gradle.
>
> I’m thrashing by trying to both update the dependencies and fix this
> problem at once, so I’ll concentrate on the dependencies tonight an
> (hopefully) get that pushed.
>
> If you have time and energy to tackle the TestKoreanTokenizer bit, that’d
> be great. Otherwise I may get back to it Friday or this weekend.
>
> Thanks!
> Erick
>
> > On Nov 13, 2019, at 6:52 PM, Anshum Gupta
> wrote:
> >
> > Hey Erick,
> >
> > Any updates on this? Just checking in and though I'm not a gradle guru,
> I'd be happy to help as much as I can :)
> >
> > -Anshum
> >
> > On Tue, Nov 12, 2019 at 7:32 PM Erick Erickson
> wrote:
> > Final note before I turn in. “ant -Dtestcase=TestKoreanTokenizer” fails
> OOB on the gradle_8 branch with:
> >
> > java.lang.RuntimeException: Cannot find userdict.txt in test classpath!
> >
> > I see on master that that file is copied into
> >
> lucene/build/analysis/nori/classes/test/org/apache/lucene/analysis/ko/userdict.txt
> >
> > I’ll look at it more tomorrow.
> >
> > After that gets fixed, and pending the bits about asciidoctorj, I think
> it’s close to ready to push to master and iterate there.
> >
> > Erick
> >
> > > On Nov 12, 2019, at 4:35 PM, Dawid Weiss
> wrote:
> > >
> > > Oh, sorry -- I thought you meant this line to be added to the main
> > > dependencies section (not buildScript's).
> > >
> > > D.
> > >
> > > On Tue, Nov 12, 2019 at 10:14 PM Anshum Gupta
> wrote:
> > >>
> > >> I didn't add this. This is already in the gradle_8 branch.
> > >>
> > >> What branch are you looking at? Don't you see this too ?
> > >>
> > >>
> > >> On Tue, Nov 12, 2019 at 12:56 PM Dawid Weiss
> wrote:
> > >>>
> > Looking at the following file:
> > solr/solr-ref-guide/build.gradle
> >
> > I see the apparently missing dependency:
> > >>>
> > >>> The buildscript dependency is there because, well, we use it from the
> > >>> script itself.
> > >>>
> > >>> For the "tools" configuration classpath the dependency is not
> missing,
> > >>> it's correct without the
> > >>> version number (palantir's plugin resolves it):
> > >>>
> > >>>tools('org.asciidoctor:asciidoctorj')
> > >>>
> > dependencies {
> > classpath "org.asciidoctor:asciidoctorj:1.6.0-alpha.5"
> > }
> > >>>
> > >>> This isn't correct, don't add it. The existing config in that script
> > >>> is fine (and works for me); I think Erik's problem is caused by
> > >>> something else.
> > >>>
> > >>> D.
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > >>> For additional commands, e-mail: dev-h...@lucene.apache.org
> > >>>
> > >>
> > >>
> > >> --
> > >> Anshum Gupta
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > > For additional commands, e-mail: dev-h...@lucene.apache.org
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >
> >
> >
> > --
> > Anshum Gupta
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
--
Anshum Gupta
