Make ReadinessLevel's configurable

[mdedetrich]

Removes Lightbend hardcoded values for readinessLevel's and allows them to be configurable. This is done by adding a new sbt key called readinessLevels which is a Map[String, ReadinessLevel] where the String is the config key in project-info.conf and the value is a Scala type that implements ReadinessLevel. I decided to make this confgurable via sbt settings instead of typesafe config because the typesafe config inheritance doesn't via nested projects doesn't work with sbt plugins (ontop of this defining the html rendering via name in hoconf is not that nice).

In order to test that this is actually working properly, I created a sample https://github.com/mdedetrich/sbt-paradox-lightbend-project-info and using sbt localPublish along with temporarily setting the version to -SNAPSHOT I republished https://github.com/akka/akka-paradox locally to test it with https://github.com/akka/alpakka docs/makeSite. Note that https://github.com/mdedetrich/sbt-paradox-lightbend-project-info implements the sbt-plugin to automatically trigger when you include it as a dependency (the alternative is to use noTrigger which means you manually have to enable it with .enablePlugins(LightbendParadoxInfoPlugin)).

This means that once this pull request and released the following things to need to be done

• Create a new project such as https://github.com/mdedetrich/sbt-paradox-lightbend-project-info that uses the newly released sbt-paradox-project-info. Note that you can just copy https://github.com/mdedetrich/sbt-paradox-lightbend-project-info if you wish, its pretty much ready to go and just needs to be put under lightbend org + released
• Update https://github.com/akka/akka-paradox to point to sbt-paradox-lightbend-project-info instead of sbt-paradox-project-info and make a new release
• Gradually update akka/lightbend projects to use the newly released akka-paradox. This is very easy due to the fact that https://github.com/mdedetrich/sbt-paradox-lightbend-project-info automatically triggers when you include it as a dependency (even as a transitive one) so all you need to do is to just bump the value of a single dependency in project/plugins.sbt.

Resolves: https://github.com/lightbend/sbt-paradox-project-info/issues/17

[mdedetrich]

Thanks for the merge, let me know when a a new release is made and what you plan to do regarding https://github.com/mdedetrich/sbt-paradox-lightbend-project-info

[ennru]

Releasing has started and I created and (so far) empty https://github.com/lightbend/sbt-paradox-lightbend-project-info.

[mdedetrich]

@ennru So it turns out you cannot fork an empty repo https://stackoverflow.com/questions/39013301/how-do-i-fork-an-empty-repository-on-github . Can you just add a LICENSE file and then I can add the rest?

[ennru]

I pushed the contents from your repo there.

[mdedetrich]

Perfect thanks, just created a PR on https://github.com/lightbend/sbt-paradox-lightbend-project-info/pull/1 that points to this new release.