-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jgitver configuration is not considered when building #154
Comments
Can you provide a reproducer ? |
Sure, just created https://github.com/igroeg/testing-jgitver/tree/master/test-123 this repo, my maven is |
@igroeg the result looks correct. What is the problem you have? the
now the computed version has a qualifier built from the branch name |
Maybe it's my misunderstanding, but I expected when you have not qualifying branches, just don't apply the plugin at all and just use the default version inside the pom? |
@igroeg that's not how it works, If you use a CI, you can skip jgitver for some branches to reach your goal, just pass |
@McFoggy I want to configure jgitver as follows - for branch master use provided hardcoded version (or i could try to disable the extention in the CI, it's not a problem at all. But then I want for all other branches the version to be branch-tag-snapshot. Is it possible at all? |
I'm using maven 3.6.3 with java 8 and started to use jgitver. The plugin seems to work fine, but doesn't ignore nonQualifierBranches. I tried to edit the configuration inside jgitver.config.xml but it really doesn't matter what I'm configuring, it's not considered at all. The configuration is as follow
The text was updated successfully, but these errors were encountered: