In my testing, the update fails and you are not presented with the option by the validator to chose rewrite the files.
On Friday, June 3, 2016 at 4:00:50 PM UTC-5, Artem Zinnatullin wrote: > > At least in previous versions of AS and Idea I was receiving updates when > I had modified files and update resolver had an option to rewrite changed > files. > > You can try to write a script to add self-signed certs to bundled JDK, > then when an update occurs — chose rewrite files, finish the update and run > your script! Or just remove old AS, install updated and run script. > > On Friday, June 3, 2016 at 11:01:07 PM UTC+3, Dallin Wilcox wrote: >> >> Android Studio 2.2 now includes a bundled JDK (as announced on the >> download page >> <http://tools.android.com/download/studio/builds/2-2-preview-2>). >> >> In an environment that requires adding self-signed certs to the JDK >> keystores for the tooling to work correctly, we would need to add our certs >> to the keystore. As we've seen in the past, when files within the Android >> Studio directory are modified, the validation that takes place during >> Studio's updates will fail the update if changes are detected (see Help, I >> Already Edited the IDE Installation Files section of the Android Studio >> Configuration page <http://tools.android.com/tech-docs/configuration>). >> >> My question is twofold - 1 will adding new certs to the embedded JDK's >> keystore break updates? and 2, if so, what other alternatives would be >> available to using the embedded JDK with a self-signed cert (aside from >> including it in the user's .AndroidStudio folder, that's not a viable >> option that can easily be scripted into a package install for a box that a >> developer may not have logged into yet). >> >> I'd love to test this one myself, but without the next update available >> yet, it's not really possible. >> > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
