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
Hi, I've just tested your plugin and the management of flavours is great for our project.
Have you planned to upgrade the plugin to add a method to increment the versionName too ?
It will be great to be able to update the versionName attribute with patch, minor or major option to increment the version (2.0.0=>2.0.1 for a patch, 2.0.0=>2.1.0 for a minor and 2.0.0 => 3.0.0 for a major).
Another plugin exists to update this version name but it does not support flavour and my issue has not been treated.
The text was updated successfully, but these errors were encountered:
@cyrillekrasinski may I know how were you able to manage the flavors for it?
I can see that there is a field called ext_constant_name that is supposed to help define the flavor.
This plugin is missing documentation, can you show an example of your Fastfile and the gradle that uses flavors ?
Would you call this plugin manually to set the versionName?
Setting the marketing version aka versionName seems to be a task, which only needs to be executes one in a while and not on every build.
Do you have a usecase, where this feature would be handy?
And I guess, if I decide to implement this, it might be a standalone plugin.
Hi, I've just tested your plugin and the management of flavours is great for our project.
Have you planned to upgrade the plugin to add a method to increment the versionName too ?
It will be great to be able to update the versionName attribute with patch, minor or major option to increment the version (2.0.0=>2.0.1 for a patch, 2.0.0=>2.1.0 for a minor and 2.0.0 => 3.0.0 for a major).
Another plugin exists to update this version name but it does not support flavour and my issue has not been treated.
The text was updated successfully, but these errors were encountered: