jgitver / jgitver/jgitver-maven-plugin
git submodules have the wrong version
Open
- Dominant language
- Groovy
- Stars
- 166
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Usecase:
- parent-project with jgitver activated
- module1 is added as a git submodule: `git submodule add path/to/module1.git`
=> parent-project and module1 are in two distinct git repositories, and have their own tags
if parent-project is tagged v1.0.0
and module1 is tagged v2.0.0
then I expect jgitver to release module1 in v2.0.0
but module1 takes the tag from the parent-project and is tagged v1.0.0 :-(
is there a way that jgitver takes the tag of the module1 repo ?
Contributor guide
Assessment
This issue has not been assessed yet.