raboof on v1.0.2
raboof on master
Fix invalid .git capture Fixes… Merge pull request #194 from ra… (compare)
git statusfrom inside the shell when in
sbt. However, I am confused as to how to use the versioning feature of this plugin. in my
build.sbti have a hardcoded value
version := "1.1.5". I don't want this hardcoded value but rather want it generated from this plugin. Is this possible to do ?
vals in the exported object, let me check it for ya: https://github.com/sbt/sbt-git/blob/master/src/main/scala/com/typesafe/sbt/SbtGit.scala#L14
gitCurrentTagswhich gives you a
git.gitCurrentTagsas a SettingKey
reloadto update those values...
git describewithin a custom sbt task that would have to invoke the corresponding sbt command, provided by the plugin... I did go that path for some things and it's not too pretty, but it should be feasible... the complicated piece with sbt is that you want to call a command (that needs a build state) from a task, which has none. There's a Task already to get the state, but I couldn't yet figure out how to read sbt's logged output for the describe command as something that the task can return as a value...
git add .,
git commit -m “added sb-git”,
git pushworked successfully
git commit —amendafter making some more changes and it hung, I wonder if it’s because it wants to open my
$EDITORand doesn’t know how
I need to access the git SHA from within my code. Ideally I'd be able to access the current sha from the buildInfo object generated by the sbt-buildinfo plugin.
I'm having a hard time.
.enablePlugins(sbtbuildinfo.BuildInfoPlugin, GitVersioning) on a common project, and
addSbtPlugin("com.typesafe.sbt" % "sbt-git" % "1.0.0") in my plugins.sbt file.
How do I now access git properties (specifically the git head sha) ?
I have a SBT project running on scala 2.11.12 and SBT 1.2.1 . I recently upgraded the SBT version to 1.3.1. Suddenly I started getting OOM error.
My SBT OPTS with SBT 1.2.1 are like this.
-J-Xms512M -J-Xmx4G -J-Xss2M -J-XX:MaxMetaspaceSize=1024M -Dhttp.nonProxyHosts=localhost
Now when I change the XX:MaxMetaspaceSize to 3072M, I suddenly see OOM vanishing.
Is it a reasonable workaround to use more Metaspace just for a newer SBT version ?