Dawid: Cassandra is away for a bit, so I created SOLR-13922 and assigned it to you. I don’t have much real understanding of the problem so the JIRA statement may need amending.
Best, Erick > On Nov 12, 2019, at 4:05 AM, Dawid Weiss <dawid.we...@gmail.com> wrote: > >> There’s one current problem with it, which may be something in my env: in >> the grade_7_refguide branch the HTML files were generated in >> ./solr/solr-ref-guide/build, but now they are in the top-level ./build >> directory. > > I think Mark has configured gradle defaults to be specifically this way. > >> I generally don’t really care where it gets built, but there are a few >> places in the docs where we pull in source code and those now throw an error >> because the path to the files is wrong. If the Ref Guide is going to get >> built there forever, it’s a tiny & simple fix to change the path, I just >> need to know if that’s the plan or if it’s a mistake. This problem also does >> not need to hold up merging that branch to master. > > Ideally, Gradle tasks consume not explicit paths but configuration > artifacts or "outputs" of other tasks. This is elegant and > error-resilient. We can clean it up as we go -- feel free to create a > task in jira and assign it to me and I'll take a look. > > D. > > --------------------------------------------------------------------- > 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
