Lol, should have read this one first. I had a plugin for 0.7 but I am only just working on 0.1x now. I'll chat on the sbt group after I've done it.
Sbt questions are probably better off being asked on the sbt mailing list though.
Thats nice, but isn't great for offline viewing, a bulk replace of a
dummy url token fixes that up nicely.
to fill that out a bit, I've made a partial migration and added
handling of multi-sub projects:
https://github.com/chris-twiner/scalesXml/blob/fullDocs/project/FullDocProject.scala
This approach uses sxr to display hyperlinked code and does a "smart"
replace. Many thanks to Jason for the fullDocs approach itself. The
benefit being that it can be used offline locally and packaged or via
a central website as well.
I have to make it less chatty (turn the content to debug only form
repointSxr) and handle .java files (not just scala ones) - but I'll
get round to that in the next days - I want at least the combined docs
and sxr for the Scales Xml 0.3 release.
Your text editor and your SBT instance disagree [1] on the encoding of
the file. Either add -Dfile.encoding=UTF-8 to your SBT options, or
stick to ASCII and represent \u20AC rather than €. [2]
-jason
[1] https://github.com/scalaz/scalaz/issues/80#issuecomment-4312538
[2] http://www.joelonsoftware.com/articles/Unicode.html
On Sun, Mar 4, 2012 at 11:24 PM, Jason Zaugg <jza...@gmail.com> wrote:
> The correct setting is:
>
> scalacOptions in (Compile, doc) <++= (baseDirectory in
> LocalProject("myRootProject")).map {
> (bd: File) => Seq[String](
> "-sourcepath", bd.getAbsolutePath,
> "-doc-source-url",
> "https://github.com/scalaz/scalaz/tree/scalaz-seven€{FILE_PATH}.scala"
> )
> }
>
> If you have a single module project, you could simplify to:
>
> scalacOptions in (Compile, doc) <++= baseDirectory.map {
> (bd: File) => Seq[String](
> "-sourcepath", bd.getAbsolutePath,
> "-doc-source-url",
> "https://github.com/scalaz/scalaz/tree/scalaz-seven€{FILE_PATH}.scala"
> )
> }
>
> -jason
Mike