Fixed
Status Update
Comments
xo...@google.com <xo...@google.com>
xo...@google.com <xo...@google.com> #2
I have submitted a fix for this for Flamingo. Should we cherry-pick it to Electric Eel?
xa...@google.com <xa...@google.com> #3
isn't the settings new in 7.4? I think the migration from non-stable version is unfortunate but less of an issue.
If we have project with stable settings plugin in 7.3 that's more a problem and we should cherry-pick.
xo...@google.com <xo...@google.com> #4
I don't know of any projects with settings plugins in 7.3, but note that if we don't have it in the Electric Eel sources we will be unable to upgrade e.g. 7.4.0 to 7.4.1.
xa...@google.com <xa...@google.com> #5
Can you point me to the change that fix this in F so that we can see if we can safely take it in EE?
xo...@google.com <xo...@google.com>
ha...@gmail.com <ha...@gmail.com> #7
=-\
;uytyujiuoilklkiuyk,iuy
;uytyujiuoilklkiuyk,iuy
Description
If you have a project with the settings plugin applied, and the assistant has to upgrade your project, it will not change the version of the settings plugin.
I had a project with using 7.4.0-alpha02 in build file and in
settings.gradle
, and it triggered a forced upgrade when opening with Flamingo Canary 2.The assistant changed the version of the app and library plugin in
build.gradle
but leftsettings.gradle
untouched.The content of that file had this section: