Ches Martin

Make commit & tag messages build-level settings

4

I end up doing this in every project where I use sbt-release: ```scala lazy val releaseSettings = Seq( // Commit messages should use imperative mood releaseTagComment := s"Release ${(version in...

Implement `docker-compose down [--volumes]`

4

The plugin currently implements the `dockerComposeStop` command, which ultimately runs `docker-compose stop`, but it also deletes the stopped containers, their *anonymous* volumes, and the network for the Compose project instance...

Consider Docker labels in lieu of "custom tags"

2

I'm evaluating sbt-docker-compose and the primary thing that first attracted me to it—as opposed to possible alternatives like [docker-it-scala] which leaves me to duplicate container definitions in yet another config...

It appears that #20 intended to remove `other_locations` as superseded by `trace`, but it left the old entry (only) in the example JSON object. An expanded section describing `other_locations` was...

When running in a console instead of notebook, e.g. `jupyter console --kernel=haskell`, the `:doc` and `:hoogle` commands output raw HTML, which isn't so useful in a terminal :smile: It would...

### Problem Out of the box, the `source` and `browse` utilities are broken: ``` $ amm --no-home-predef Loading... Welcome to the Ammonite Repl 2.5.2 (Scala 2.13.8 Java 11.0.12) @ source(new...

Fails to run in test configuration scope despite correct test:reStart::mainClass

1

For esoteric reasons (but reasonable ones can probably be imagined), I have some projects with executable classes living in the sbt test configuration. `test:run` works fine and `show test:reStart::mainClass` is...

Breaks on macOS/BSD: non-portable split options

3

Hi, thanks for this plugin. Unfortunately as the title says, it breaks on macOS/BSD because of the usage of `split`: https://github.com/alx741/vinfo/blob/3471cd547b591dcbcaf524a06c1f3423d8650b5d/autoload/vinfo/repo.vim#L35 The `-d` and `--additional-suffix` flags are GNU-specific, they're [not...

I have a situation where leaf application modules in a multi-module/Reactor build target Java 11, but a particular module needs to continue being able to run in Java 8 runtime...

If `xml:lang` is kept, `lang` must also be used _and they must be exactly the same_. This was failing validation out of the box. The `xmlns` and `xml:lang` are no...