BuildInfo.buildInfoBuildNumber DRY about sbt-buildinfo HOT 2 CLOSED

This is because the plugin's key for the build number is namespaced as buildinfo-buildnumber, and identifiers are autogen'ed by camel casing the sbt key, thus buildinfoBuildnumber.

There's a construct to define a custom field name using tuple, but it won't work either since buildInfoBuildNumber is a task (value could change every time) but buildInfoKeys is a setting (value is set at build definition time).

I don't want to introduce a special rule that'll break existing user's source, so I don't think there's much we can do.

from sbt-buildinfo.

I forgot about BuildInfoKey.map. This works:

  BuildInfoKey.map(buildInfoBuildNumber) { case (k, v) =>
    "buildNumber" -> v
  }

from sbt-buildinfo.