You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The versioning logic is currently a bit awkward, with the CI creating new branches/committing/pushing on its own for the sole purpose of versioning.
A simpler approach would be to use jvm properties in order to dynamically resolve the version using some logic around git describe.
You could imagine providing a build script which would essentially redirect the args it gets called with to mvn -Drevision={insert_dynamic_version}, making the version easily reproducible/inspectable locally.
The text was updated successfully, but these errors were encountered:
The versioning logic is currently a bit awkward, with the CI creating new branches/committing/pushing on its own for the sole purpose of versioning.
A simpler approach would be to use jvm properties in order to dynamically resolve the version using some logic around
git describe
.You could imagine providing a
build
script which would essentially redirect the args it gets called with tomvn -Drevision={insert_dynamic_version}
, making the version easily reproducible/inspectable locally.The text was updated successfully, but these errors were encountered: