moleksyuk / vcs-semantic-version Goto Github PK

If we have many developers with many branches (or just many branches), then sometimes it is hard to detect which build is exactly makes the problem.
Could you add the option to generate the hashes (if VCS supports this), not the numbers?

The command for git

$ git rev-list HEAD -1
e03e23107dc98f8792ef0bbde0270c7875a251b6

Or the shortest hash

$ git rev-list HEAD --abbrev-commit -1
e03e231

Set major/minor as '0'.

Actual:

:buildSemanticVersion FAILED

FAILURE: Build failed with an exception.

* What went wrong:
'minor' property is required.

Expected: project.version is populated in right way.

https://plugins.gradle.org/docs/publish-plugin
https://plugins.gradle.org/docs/publish-plugin

v.1.0.1 is broken due to missed property files in META-INF for gradle plugin class definition.

Hi,
I am trying to configure your plugin for a root/sub projects configuration.
I have a root empty project, and I want to apply version on all sub projects, but it seams that I have missed something. I tried different writings of my build.gradle, but either your plugin complains about missing major/minor, or when publishing with maven, I have no version at all, or your plugin does not find which vcs it is (seams that it checks the current project, not the root)

What would be a full sample of a working root/sub projects, with maven publish version set with almost everything set in root project (publish, version), only dependencies in sub projects...

Thanks.

v.1.1.2 doesn't work with java 1.7