sbt-site | Site generation for sbt | Static Site Generator library

by sbt Scala Version: v1.4.1 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | sbt-site Summary

sbt-site is a Scala library typically used in Web Site, Static Site Generator, Jekyll applications. sbt-site has no bugs, it has no vulnerabilities and it has low support. However sbt-site has a Non-SPDX License. You can download it from GitHub.

This sbt plugin generates project websites from static content, Jekyll, Sphinx, Pamflet, Nanoc, GitBook, Paradox, Hugo, Laika and/or Asciidoctor, and can optionally include generated Scaladoc. It is designed to work hand-in-hand with publishing plugins like sbt-ghpages.

Support

Quality

Security

License

Reuse

Support

sbt-site has a low active ecosystem.

It has 173 star(s) with 74 fork(s). There are 19 watchers for this library.

It had no major release in the last 12 months.

There are 26 open issues and 45 have been closed. On average issues are closed in 208 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of sbt-site is v1.4.1

Quality

sbt-site has 0 bugs and 0 code smells.

Security

sbt-site has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

sbt-site code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

sbt-site has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

sbt-site releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of sbt-site

Get all kandi verified functions for this library.

sbt-site Key Features

No Key Features are available at this moment for sbt-site.

sbt-site Examples and Code Snippets

No Code Snippets are available at this moment for sbt-site.

Community Discussions

Trending Discussions on sbt-site

how does the sbt plugin versioning scheme worK?

Access file names(or mappings) from specific dependency in sbt

How to declare a sbt plugin?

QUESTION

how does the sbt plugin versioning scheme worK?

Asked 2018-Apr-29 at 03:37

For sbt 0.13, we publish sbt plugins that are versioned 0.13, and for sbt 1.0.x, we published sbt plugins that are versioned 1.0. However, for sbt 1.1.x, it seems like we publish sbt plugins that are versioned 1.0 too. For example, the latest sbt-site is published with a 1.1.x version, but it only publishes 0.13 and 1.0 versions. How does sbt plugin versioning work for sbt 1.x.x?

...

ANSWER

Answered 2018-Apr-28 at 22:03

Before 1.0 versioning API was not guaranteed to be stable (within major version). sbt iterated on minor version, so between 0.12, and 0.13 lines there could be breaking changes - though developers tries to avoid them if they didn't bring any value to the table, and within minor version line (e.g. 0.13.0, 0.13.1, 0.13.2, ... 0.13.15) they did their best to don't break changes.

0.13.x line was actually kind of stable - most of the time you could upgrade thing without much issues, and (I might be wrong here but) usually any braking changed were either bugs, or fixes to invalid behavior.

1.0 broke compatibility with 0.13. The biggest one was change from Scala 2.10 to Scala 2.12. Since it was deemed actual, mature release, authors could commit and guarantee backward compatibility within major version, so plugins written for 1.0 will work with 1.1, 1.2 etc. One exception I remember is addition of unified slash syntax in 1.1.2 - if you use in your build or plugin it you force usage of sbt at at least 1.1.2. Other than that I cannot remember anything big.

Since the change from 0.13 to 1.0 is quite a big one for community (basically each plugin need to either be migrated and/or cross compiled), some people might stay for a while on 0.13 line. That's the main reason why it is still supported.

For any practical purpose I would assume that right now you can publish and use any plugin intended for 0.13 with latest 0.13 versions, and any plugin published for 1.0 (that do not use unified slash syntax) to be usable by any 1.0 version: 1.0.x, 1.1.x, 1.2.x, ...

Source https://stackoverflow.com/questions/50080942

QUESTION

Access file names(or mappings) from specific dependency in sbt

Asked 2017-Sep-20 at 11:08

I would like to access all of the content of one of my dependencies during the build. To be more precise, I want to include the scaladoc of one of my dependencies into a site generated with sbt-site. I think I could do that with mappings or addMappingsToSiteDir as described here but for that I need to be able to get mappings of this dependency somehow.

...

ANSWER

Answered 2017-Sep-20 at 11:08

I have solved the problem with following code.

Source https://stackoverflow.com/questions/46237695

QUESTION

How to declare a sbt plugin?

Asked 2017-Jan-10 at 08:54

I have cloned sbteclipse.I am reading scala-sbt tutorial,says:

...

ANSWER

Answered 2017-Jan-10 at 08:54

As a general rule, SBT plugins has to be defined in the project subfolder of your project's root. SBT aggregates definitions from all files with .sbt extension, so it doesn't really matter if you call it plugins.sbt or site.sbt. It's also fine to have multiple .sbt files.

So in your particular case, either add that plugin to the existing project/plugins.sbt, or follow the tutorial and create a new file, project/site.sbt, and add the plugin there.

P.S. this rule of searching and aggregating definitions from all .sbt files applies not only to meta-build (project directory), but also for the build itself. It might make sense to split big build definitions into multiple .sbt files. E.g. we have build.sbt for main definitions (library dependencies, etc.) and docker.sbt for Docker definitions.

Source https://stackoverflow.com/questions/41554490

Community Discussions, Code Snippets contain sources that include Stack Exchange Network