-
Notifications
You must be signed in to change notification settings - Fork 47
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
Versioning compatibility with ivy2/maven wildcard patterns for first snapshot build after tag #52
Comments
Interesting. Here are the relevant cases:
Perhaps we can change that first one so it's:
|
Yup, that should work perfectly. |
leonardehrenfried
added a commit
to leonardehrenfried/sbt-dynver
that referenced
this issue
Feb 17, 2018
leonardehrenfried
added a commit
to leonardehrenfried/sbt-dynver
that referenced
this issue
Feb 25, 2018
dwijnand
pushed a commit
that referenced
this issue
Feb 27, 2018
Use 'git describe --long' to get SHA1 on dirty tag. Fixes #52
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm loving this plugin, but I'm looking for a way to easily use it with dependency wildcard patterns in ivy and maven.
the current versioning pattern means that the first "snapshot" version after a tag is
0.0.1+20171207-1200
; while the first committed version after a tag is0.0.1+1-01234abcd
This means that a version spec like "0.0.1+" will select the older, snapshot, version over the newer version.
This could be solved just by changing the first snapshot build after a tag to use
0.0.1+0+20171207-1200
I know I can customize my version string - but this seems like a wide use case.
The text was updated successfully, but these errors were encountered: