@dwijnand would you welcome a pr that automates the release with
sbt-release?
For the record, the process is currently: bump the version in the README (edit and commit), git tag the repo, load (or reload) the build in sbt, run
publish.
Maybe Heiko knows.
@dwijnand automatically setting the version in the readme during release is possible with a hacky parse-and-replace step. do you prefer that or would you be okay with a badge that shows the current version like i did here: https://github.com/leonardehrenfried/play-json-traits/
I was going to suggest adding a little comment to that part of the readme to avoid regressions in the feature (like coursier does https://github.com/coursier/coursier/blob/7b1bbae2085bbcc075c803ce3aaf15c6b9bd80f4/project/plugins.sbt#L23) but it turns out that comments in markdown aren't supported, and the workarounds involve abusing the link syntax: http://stackoverflow.com/questions/4823468/comments-in-markdown -.-
It seems that the recommendation for suppressing DEBUG messages from jgit is to import the no-op slf4j jar, but we have internal sbt plugins that import an actual logging backend, so that’s not an option for us. Is there another way to change the slf4j loglevel to suppress those messages?
FWIW, I was able to add a
logback.xml config file (since we’re using logback as the slf4j backend) to another sbt plugin and use it to configure the logging from sbt-git. For some reason adding logback.xml to the sbt meta-build of the project including sbt-git didn’t work (I suspect because of a classloader conflict), but for my purposes adding the file to the plugin actually works better anyway, so that’s fine.
@dwijnand Thanks. I tried that, but it didn’t load it. I can’t find the specific code now, but I was able to define a task in a
build.sbt that could use the classloader to load from project/src/main/resources, but the classloader used by the logger factory inside jgit did not have any classes or resources defined in project. It did have the jars of all the sbt plugins, though, which is why adding the file as a resource to a plugin worked.
or I should say /project
yeah that doesn't go in project
I put it in /
seems to work but I haven't tested it
Really just using this plugin to see if I can collect the branch names from it. Can I collect the branch names from it?
in a variable or val to work with publish?
git status
Error: Could not find or load main class org.eclipse.jgit.pgm.Main
[error] Nonzero exit code (1) running JGit.
I'm going to assume that I need to add JGit as a dependency. Not sure why that's not in the docs
Or can you give an example?
Think I only need it for the build steps.
to be honest if all you need is a little piece of git usage I'd just use the process api, something like:
scala> scala.sys.process.Process("git rev-parse --symbolic-full-name --abbrev-ref HEAD").!!.dropRight(1)
res0: String = master
So I get the branch information in my shell prompt
Think that comes from enablePlugins(GitBranchPrompt)
Also enabled enablePlugins(GitVersioning)
And the useJGit in git.sbt as discussed above
But I still get
git status
Error: Could not find or load main class org.eclipse.jgit.pgm.Main
[error] Nonzero exit code (1) running JGit.