Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support scaladoc for subprojects #55

Closed
dwalend opened this issue Oct 1, 2015 · 2 comments
Closed

Support scaladoc for subprojects #55

dwalend opened this issue Oct 1, 2015 · 2 comments
Milestone

Comments

@dwalend
Copy link

dwalend commented Oct 1, 2015

Putting site.includeScaladoc() in the top build file wasn't enough to get the scaladocs for the whole project included in site.

Including sbt-site and the site.includeScaladoc() setting in subprojects gets the scaladoc into the zip file. However, that's not useful for putting together a zip file for the whole site.

Please add something to include subprojects' scaladocs via the top-level package-site command. I suspect each subproject should be able to include or exclude itself from the site, with everything included by default.

Thanks,

Dave

@metasim
Copy link
Member

metasim commented Mar 2, 2016

Note to contributors: Need to create a scripted test for this scenario and see if it can be done with a combination of the new autoplugin-based configuration and custom Config definitions.

@jonas
Copy link
Member

jonas commented Sep 2, 2016

@dwalend Did you consider using https://github.com/sbt/sbt-unidoc?

On a related note, we should add a test for using sbt-unidoc and maybe submit an to update its example. This is also a good use case for testing #60

jonas added a commit to jonas/sbt-site that referenced this issue Dec 16, 2016
It changes the SiteScaladocPlugin to provide a scaladocSettings method
to aid in mapping Scaladoc to a site. Adds examples for using sbt-unidoc
as well as a solution for separate Scaladoc as requested in sbt#55.
@jonas jonas mentioned this issue Dec 16, 2016
@jonas jonas added this to the 1.2.0 milestone Dec 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants