It's fine, I have no idea either. The question was an honest one. On Wed, Apr 15, 2015 at 10:48 AM Treggiari, Leo <leo.treggi...@intel.com> wrote:
> If anyone has the time to educate me, then please pardon my ignorance. > > Then you're suggesting that if I'm writing a cross-platform app, I stick > with > the legacy whitelist plugin until all of the platforms I care about support > new whitelisting? Or they already do support the new whitelisting? > > Thanks, > Leo > > -----Original Message----- > From: Joe Bowser [mailto:bows...@gmail.com] > Sent: Wednesday, April 15, 2015 10:42 AM > To: dev@cordova.apache.org > Subject: Re: Android 4.0 Blog Post > > Isn't this why the Legacy Whitelist plugin exists? > > On Wed, Apr 15, 2015 at 10:40 AM Treggiari, Leo <leo.treggi...@intel.com> > wrote: > > > I have a question. With the new whitelist support in Android, does that > > mean if I'm writing a cross-platform app, do I need to deal with > > whitelisting differently in Android and other platforms (at least until > the > > other platforms 'catch up')? If not, thanks. If so, what would be the > > best way to handle the differences - perhaps using the merges > functionality? > > > > Thanks, > > Leo > > > > -----Original Message----- > > From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew > > Grieve > > Sent: Wednesday, April 15, 2015 10:18 AM > > To: dev > > Subject: Android 4.0 Blog Post > > > > The 4.0 release is posted to npm, and I've updated the blog post to work > > without the need for a tools release: > > > > I'd like to publish the blog post without waiting for a CLI release: > > - I've updated the post to use plugins-from-git so it works without new > CLI > > - I've mentioned those can just wait for tools if they like > > - This should give us some early adopter feedback in case there's a need > > for a 4.0.1 > > > > > > > https://github.com/cordova/apache-blog-posts/blob/master/2015-04-10-cordova-android-4.0.0.md > > > > Any objections? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > >
