Thank you Munendra, Jason, Erick and Alex for the pointers and extra context!
The techproducts example is once again running fine for me locally now then. :) From: [email protected] At: 09/24/20 16:02:27To: [email protected] Subject: Re: bin/solr testing surprise with techproducts example I run ./gradlew -p solr/packaging assemble . I think that shows when you do ./gradlew helpWorkflow (one of many help commands added for our projects). And it will be in solr/packaging/build/solr-9.0.0-SNAPSHOT I need to experiment more with ./gradlew dev command, if it does not do full wipe out, that could be useful. I also use "git worktree" as I have maybe 4 Jiras worked on in the same timeframe, plus I want to compare to baseline master build when I screw things up. Apparently, IntelliJ Idea terminal will even remember open locations in the project file, so the worktrees help to reopen everything in issue-appropriate directories (still learning to take advantage of that). Regards, Alex. On Thu, 24 Sep 2020 at 10:51, Erick Erickson <[email protected]> wrote: > > Christine: > > Quite possibly you had some remnants of an ant build hanging around from bin/solr. If I start with a fresh clone and try to start from bin/solr I usually get no class def errors. > > git clean -dxf if my friend to be absolutely sure that I have nothing laying around when switching back and forth between 8x and master, although others have suggested that git “worktree” is a much better alternative that I haven’t explored yet. I’m sure it is, because for one thing “git clean -dxf” removes any IDE files too... > > The correct place to run solr from should be under “…/master/solr/packaging/build”, the “dev” and “assemble” targets will go into different directories. “assemble” will wipe out anything that used to be, the “dev” won’t, which will preserve directories, indexes and the like. Definitely preferable for code change iterations. > > Finally, there was a helpful message telling you where the artifacts were that got lost, it’ll get put back sometime. See SOLR-14888 > > Best, > Erick > > > On Sep 24, 2020, at 9:14 AM, Jason Gerlowski <[email protected]> wrote: > > > > I couldn't reproduce your error on running techproducts. Though > > whatever is causing it locally for you sounds a bit related to > > SOLR-13690 maybe? > > > > Jason > > > > On Wed, Sep 23, 2020 at 11:28 AM Munendra S N <[email protected]> wrote: > >> > >> The wiki has steps to build solr with gradle > >> https://cwiki.apache.org/confluence/display/SOLR/Building+Solr+with+Gradle > >> > >> ./gradlew assemble or ./gradlew dev will create runnable solr instance. > >> > >> > >> On Wed, Sep 23, 2020, 8:01 PM Christine Poerschke (BLOOMBERG/ LONDON) <[email protected]> wrote: > >>> > >>> Hello everyone. > >>> > >>> So I was trying to locally test the small https://issues.apache.org/jira/browse/SOLR-11167 change on master branch and encountered two things: > >>> > >>> Question: What is the replacement for "cd solr ; ant dist server" usage? > >>> > >>> If there is an equivalent -- "./gradlew -p solr assembleDist" perhaps? -- then I'd be happy to update https://github.com/apache/lucene-solr/blob/master/help/ant.txt with the info. > >>> > >>> Observation: "cd solr ; bin/solr start -e techproducts" on master branch (but not branch_8x) gives me an error. Is this a known issue already or if not could someone try to reproduce the issue before a JIRA ticket is opened? > >>> > >>> ERROR: Error CREATEing SolrCore 'techproducts': Unable to create core [techproducts] Caused by: [schema.xml] analyzer/tokenizer: missing mandatory attribute 'class' > >>> > >>> Thanks, > >>> > >>> Christine > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
