Local Publish uses different timestamp for each module
jeddai opened this issue · 0 comments
One viable workflow when trying to build android-components changes for Fenix/Focus is making the change, then running ./automation/publish_to_maven_local_if_modified.py
, then updating the Fenix android-components version to match the version that was just created in your local maven repository.
The issue here is that each module published by the project ends up having a totally different version number, so the version substitution doesn't work.
In the various publish
and build
gradle files in the repository, there is a line that determines the version when publishing. At the moment, when the local
property is set, it uses a timestamp generated by groovy. The local
property is a timestamp defined by the Python function, so these cases should be updated to use the local
property instead of a runtime-generated timestamp.
Working example in application-services
┆Issue is synchronized with this Jira Task