Colin Dean
Colin Dean
I'm not sure what else I can change. @mbrannstrom @mojocinn, what version of Gradle are you using?
OK, some progress: ``` groovy buildscript { repositories { maven { url "https://plugins.gradle.org/m2/" } } dependencies { classpath "com.cinnober.gradle:semver-git:2.2.2" } } plugins { id 'java' // id "com.cinnober.gradle.semver-git" version "2.2.2"...
Probably the take-away from this is a modification to the README which states NOT to use the newer `plugins` way of including it.
Thanks for the insight. On Apr 12, 2016, 01:48, at 01:48, "Mikael Brännström" [email protected] wrote: > The newer way `plugins { id .. }` has other problems as well. For...
I just got bit by this again on a new project. Is there any way to detect that it's running, or perhaps output some debug logging to show what it's...
Came looking for exactly this feature!
Commenting to connect this with the one about Org Charts: https://github.com/mermaid-js/mermaid/issues/1360
Could this PR also remove the strip step from release builds? https://github.com/typst/typst/blob/045a109600fa9127d22259287bbde62234cadb44/.github/workflows/release.yml#L34-L36
@CGMossa Sorry, this does warrant more context. If you download a source archive from a release, e.g. [22-03-21-2](https://github.com/typst/typst/releases/tag/22-03-21-2), unpack, and cd into it, e.g. ```shell tag=22-03-21-2 thedir=$(mktemp -d -t typst-test-compile)...
I pretty firmly disagree. Yes, it's bringing in a bunch of stuff but virtually guaranteed all of that information is going to end up getting used. I didn't put it...