I mentioned when we chatted at activate that I had a build in the past that was doing some pulling of gems... Looked back and it was actually using https://github.com/robfletcher/gradle-compass which was doing the gem management. Seems to use https://github.com/jruby-gradle/jruby-gradle-plugin to pull gems (if I'm reading their code right). That could be helpful in automating the requirements for the html ref guide.
On Tue, Sep 17, 2019 at 1:32 PM Cassandra Targett <casstarg...@gmail.com> wrote: > I got started on the Ref Guide build last night. The biggest change there > is to use the asciidoctor-gradle-plugin instead of using the > asciidoctor-ant plugin. > > So far I’ve got it working enough to build a single page of the Ref Guide > into a PDF file. Baby steps ;) > > By itself that only gets us the PDF, while our HTML is built with several > Ruby gems which we had to require people to install locally. However, the > asciidoctor-gradle plugin includes JRuby, so fingers crossed we’ll finally > be able to get that working and end up in a better place than we are today, > and with a more unified build configuration than we currently have. > > I’m not ready to push anything to the branch yet, but hopefully will be in > the next day or two. > > Cassandra > On Sep 17, 2019, 5:02 AM -0500, Dawid Weiss <dawid.we...@gmail.com>, > wrote: > > [...] last I remember Dawid signed up for it starting around today (15th) > ;) > > > Ah... so you remembered?... Kind of hoped you forgot. :) > > I'll take a look and try to tackle some of Chris's questions. Are we > free to commit to that gradle branch or do you prefer PRs? > > D. > > --------------------------------------------------------------------- > 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)
