Is there a recommended way to manage dynamic versions when a you create a branch for release?
We currently declare all dependencies using particular revisions e.g. ‘ois:serverUtils:1.0’. We have several projects that are treated as libraries and published into Ivy and want to avoid the manual step of updating the build.gradle files in other projects which depend on these types of libraries.
Using dynamic revisions e.g. latest-integration would solve this, however this creates a problem when we create a branch (in Subversion) for a release. For the branches we need to put these dynamic versions back to the particular revisions. Is there any recommended way to do this? I’m thinking I’ll need to write my own script to do this (but haven’t figured out how yet).
What are other people doing to manage dynamic versions when creating branches?
Does Gradle provide any way to handle this? Does anyone know if a repository manager like Artifactory has any features to help with this, or plug-ins in Jenkins?