Cool, thanks Yan. With those versions, I get the same good behaviour. Jakob: yeah, it's quite standard in Ruby projects to lock down all the dependencies (because many Ruby projects suck at compatibility across versions). I've put a proposed solution here: https://issues.apache.org/jira/browse/SAMZA-297
Martin On 18 Jun 2014, at 10:42, Jakob Homan <[email protected]<mailto:[email protected]>> wrote: Can we automate getting these versions, etc.? I'm not familiar enough with the ruby toolchain to be able to reliably build these on my Mac. It'd be better if we had something akin to Gradle/maven version enforcer. -jg On Wed, Jun 18, 2014 at 9:53 AM, Yan Fang <[email protected]<mailto:[email protected]>> wrote: Hi Martin, That is a serendipity. I am using: jekyll (2.0.3) jekyll-coffeescript (1.0.0) jekyll-sass-converter (1.0.0) redcarpet (3.1.2) I think we should be able to reproduce the result with the same version. Cheers, Fang, Yan [email protected]<mailto:[email protected]> +1 (206) 849-4108 On Wed, Jun 18, 2014 at 9:16 AM, Martin Kleppmann <[email protected]<mailto:[email protected]>> wrote: > Hi Yan, > > I noticed in your last build of the Samza website that anchors for > subheadings were added based on the text of the heading. For example, "#### > Log4j configuration" becomes <h4 id="log4j-configuration">Log4j > configuration</h4>. > > That's cool, I had been trying to figure out how to do that, but couldn't > make it work! When I run jekyll I get IDs like "toc_0", "toc_1" etc, not > nicely named IDs. In order for internal links in the docs to work, we'll > have to standardise on either one or the other naming scheme, and I like > yours better. > > So I was wondering: what version of the gems are you running? Could you do > `gem list jekyll; gem list redcarpet` for me? If we can standardise on the > version that you're using, then hopefully no matter who builds the docs, > we'll get the <h4 id="log4j-configuration">Log4j configuration</h4> style > headings. > > Thanks, > Martin > >
