Scaladoc generates a listing page for every class you run it on.<\/p>\n
In this post, I’ll show how to convert the output of the entire API documentation (on the official scala site) to Markdown that is compatible with Jekyll (so that you can add \/ modify formatting as desired).<\/p>\n
I got the main scala library, forked it, and built from source. To do this, you will need some pre-requisites:<\/p>\n
\nbrew update\nbrew install ant\nbrew install gem\ngem install jekyll\n<\/pre>\nThere is an ant target that lets you generate all of the scala documentation from source (this is what you’d need if you want to keep up with the nightly builds).<\/p>\n
\ngit clone https:\/\/github.com\/garysieling\/scala.git\ncd scala\nant docs\n<\/pre>\nThis took ~40 minutes for me.<\/p>\n
To convert this to markdown, there is a handy library called “nyandoc”<\/a>, but you need to install a scala dependency tracking thing called “conscript”<\/a> first (this seems to be a wrapper around SBT).<\/p>\nThere are a couple ways to do this, and I had to fiddle with it to get it to work.<\/p>\n
You can either download the JAR and install or yolo it and get code directly from Github:<\/p>\n
\ncurl https:\/\/raw.githubusercontent.com\/n8han\/conscript\/master\/setup.sh | sh\n<\/pre>\nI had problems with both methods, but eventually got this to work.<\/p>\n
Once conscript installs it’s not on your path by default, but it’s not a big deal. You then install nyandoc with this command:<\/p>\n
\n\/Users\/gary\/bin\/cs todesking\/nyandoc\nsbt launcher version 0.13.7\n\nConscripted todesking\/nyandoc to \/Users\/gary\/bin\/nyandoc\n<\/pre>\nThis tool is also not on your path.<\/p>\n
To convert to markdown, go into the folder where you build scala, and there will be a “library” folder that has the compiled scaladoc output.<\/p>\n
\ncd scala\/build\/scaladoc\n\/Users\/gary\/bin\/nyandoc library library-markdown\n<\/pre>\nThe above command should only take a few minutes.<\/p>\n
Now, copy the output over to your jekyll site. <\/p>\n
\ncp -R library-markdown ..\/..\/..\/scaladoc-jekyll\/_posts\/\ncd ..\/..\/..\/scala-jekyll\/_posts\n<\/pre>\nScaladoc output is a deeply nested folder structure. For this example the easiest thing to do is to flatten this:<\/p>\n
\nfind *\/ -type f -exec bash -c 'file=${1#.\/}; echo mv \"$file\" \"${file\/\/\\\/\/_}\"' _ '{}' \\; > move_all.sh\nchmod +x .\/move_all.sh \nmv *.md ..\n<\/pre>\nYou still have a problem, because Jekyll expects a blog, with numbered blog posts.<\/p>\n
So, we can cheat the system by adding this:<\/p>\n
\nls | sed \"s\/\\(.*\\)\/mv \\1 2016-02-15-\\1\/\" > move_all.sh\nchmod +x move_all.sh \n.\/move_all.sh\n<\/pre>\nNow, you will have a Jekyll site with all the scala docs (one page per article).<\/p>\n","protected":false},"excerpt":{"rendered":"
Scaladoc generates a listing page for every class you run it on. In this post, I’ll show how to convert the output of the entire API documentation (on the official scala site) to Markdown that is compatible with Jekyll (so that you can add \/ modify formatting as desired). I got the main scala library, … <\/p>\n