Hi Thasso, We don't support any way to prevent the daily override. I have fixed the issue and we are working on getting a 0.4.1 release as soon as possible. I am sorry for the trouble.
Raymond On Tuesday, November 17, 2015 at 12:40:02 AM UTC-8, Thasso Griebel wrote: > > Hi, > > since yesterday, we run into the issue that the gradle plugin complains > with: > > Plugin is too old and ANDROID_DAILY_OVERRIDE value is also outdated, > please use new value :"2cde4f43d5e579fea9fd58922bee1d419dd1e07c" > > and the hash changes every day. That means that we have to touch our CI > build also every day. We are using the the experimental plugin > 0.3.0-alpha7, which is incompatible with the 1.5.0 plugin. The problem is > that we have an issue with compiling and linking against static native > dependencies (see > https://code.google.com/p/android/issues/detail?id=193751) using a > configuration like > > > model{ > android.sources { > main { > jni { > dependencies { > project ":other" linkage "static" > } > } > } > } > } > > > is working with 0.3.0-alpha7 but does not work with the 0.4.0 version. > With 0.4.0, the dependency is created, but always links against the shared > version of the dependency. I tried that using either a library or the new > native modules, but with the same effect. > > This unfortunately prevents us from updating to 1.5.0/0.4.0. Is there any > way to avoid the "Plugin is too old" message without daily updating > ANDROID_DAILY_OVERRIDE? > > Thanks, > > Thasso > -- 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.
