Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of agrieve@google.com designates
 209.85.219.41 as permitted sender)
MIME-Version: 1.0
Sender: agrieve@google.com
In-Reply-To: 
 <CADVgkyPSv-a_2NR31PBsF7XypEG3FELjemK-iStWBMRG=Nw1ng@mail.gmail.com>
References: 
 <CANpVHHxaZzqVpVHqFjgSnzvqEBix4vhznwSj9frwtXzE=C=AvA@mail.gmail.com>
 <CADVgkyPSv-a_2NR31PBsF7XypEG3FELjemK-iStWBMRG=Nw1ng@mail.gmail.com>
From: Andrew Grieve <agrieve@chromium.org>
Date: Thu, 24 Apr 2014 21:34:09 -0400
Message-ID: 
 <CABiQX1X6u0yNkV=XZNzf17vWBbfwjOEdkOaaeniQykrhDteOyg@mail.gmail.com>
Subject: Re: [JS] merging to master for cordova-js and cordova-plugman
To: dev <dev@cordova.apache.org>
Content-Type: text/plain; charset=UTF-8

Cool! Does no impact mean that browserify is still not used by
default, or does it mean that it's backward compatible?

Failing specs sounds like impact...

And it does look like medic is failing due to browserify-type things:
http://108.170.217.131:8010/waterfall

Unless you feel like powering through this tonight, I'll probably
revert in the morning so that our continuous build can stay green.

On Thu, Apr 24, 2014 at 6:06 PM, Brian LeRoux <b@brian.io> wrote:
> \o/
>
>
> On Thu, Apr 24, 2014 at 2:30 PM, Anis KADRI <anis@apache.org> wrote:
>
>> I just merged both browserify branches into master. There should be no
>> impact.
>> Right now most specs pass expect for File, FileTransfer, Media and Contacts
>> due to some issues with merges/clobbers and I am looking into those.
>>
>> Also, I got rid of the project cache condition in plugman that was
>> preventing iOS frameworks from being added (CB-6441)
>>
>> Anis
>>