As of commit f2477af4cd043db380f6ade0ebffc3acd2a1a331 the method of assigning version to an artifact will be made automatic using gradle's nebula ( https://github.com/nebula-plugins/nebula-release-plugin ) plugin.
Previously we always include version varibale on the build.gradle file. But it's not needed anymore, or rather please dont add version on build.gradle
To publish the artifact to production we now use this: https://jenkins.noc.tvlk.cloud/job/flight-backend-publish-artifact/ pipeline.
When you want to publish your artifact, you will be asked about RELEASE_SCOPE. You can fill that field with either major, minor, or patch. To learn more about Sematic Versioning you can read more at https://29022131.atlassian.net/wiki/spaces/BEI/pages/690226120/Semantic+Version+and+Compatibility+in+Java
After that the pipeline will build your changes and assign the new version according your answer.
Please read the wiki carefully before deciding the RELEASE_SCOPE of your changes
Nothing has changed on local publishing except when you publish yor artifact locally the version will be concated with -dev.<number>+<commit_id>
https://29022131.atlassian.net/wiki/spaces/BEI/pages/690029536/Introduction+to+Multi-Repository+Practice+and+old-monorepo-2017+Migration+Guide
https://29022131.atlassian.net/wiki/spaces/BEI/pages/690226120/Semantic+Version+and+Compatibility+in+Java
https://29022131.atlassian.net/wiki/spaces/BEI/pages/491127714/Dependency+Dismantling+Guide