gradle-jgitver-plugin
gradle-jgitver-plugin copied to clipboard
jgitver
gradle plugin that defines automatically project version using jgitver
What are the plans for releasing an "official" 0.10.0 version? I'm mostly interested in the update to extract the version and make it available early (i.e. not in an `afterEvaluate`...
After migrating to `main` from `master` the version string still shows the non-qualified branch name (which I changed to main). * Plugin version ```kotlin plugins { id("fr.brouillard.oss.gradle.jgitver") version "0.10.0-rc03" }...
The three default qualified version numbers (0.0.0-EMPTY_GIT_REPOSITORY, 0.0.0-NOT_A_GIT_REPOSITORY, 0.0.0-NO_WORKTREE_AND_INDEX) contain underscore characters. But underscores are not legal according to semver and npm takes this seriously: ``` # npm version 0.0.0-NOT_A_GIT_REPOSITORY...
When upgrading from 0.9.1 to any 0.10.0 release candidate the policy blocks fail to be applied. Config: ``` jgitver { policy { pattern = '(.*)' transformations = ['REMOVE_UNEXPECTED_CHARS', 'LOWERCASE_EN'] }...
update to newest jgitver, gradle version, as well remove long outdated references in the readme to ancient versions of the plugin.
when using the _buildscript_ syntax it looks like the plugin coordinates from the gradle portal have changed and now require a `gradle.plugin.` prefix. so one should now use a synatx...
We should have functionnal tests as described in https://guides.gradle.org/testing-gradle-plugins/#functional-tests instead of manual tests.
based on https://github.com/gradle-guides/testing-gradle-plugins integration testing should be automated
I want that on the development branch version automatically gets increased by **minor** version as mostly commits do include new functionality. With default configuration patch version gets increased. current latest...
