Re: Review Request 14566: plugins release - Oct 9, 2013

[Andrew Grieve]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14566/#review26849
---


Sounds good. Two things I'd change:

1. Add a note on how to upgrade plugins (via plugin rm $ID && plugin add $ID).
2. Mention that three new plugins now exist (websql for Android, keyboard for 
iOS, statusbar for iOS). 

- Andrew Grieve


On Oct. 10, 2013, 12:40 a.m., Steven Gill wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14566/
> ---
> 
> (Updated Oct. 10, 2013, 12:40 a.m.)
> 
> 
> Review request for cordova.
> 
> 
> Repository: cordova-site
> 
> 
> Description
> ---
> 
> Added the diff file that has the blog in the bottom.
> 
> Also added the .md file as a attachment.
> 
> 
> Diffs
> -
> 
>   /public/blog/index.html 1530831 
>   /public/index.html 1530831 
>   /public/news/2013/10/01/plugins-release.html 1530831 
>   /public/news/2013/10/09/plugins-release-oct-9.html PRE-CREATION 
>   /public/news/2013/10/09/plugins-release.html PRE-CREATION 
>   /public/rss.xml 1530831 
>   /www/_posts/2013-10-01-plugins-release.md 1530831 
>   /www/_posts/2013-10-09-plugins-release.md PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/14566/diff/
> 
> 
> Testing
> ---
> 
> 
> File Attachments
> 
> 
> blog post.md
>   
> https://reviews.apache.org/media/uploaded/files/2013/10/10/2013-10-09-plugins-release.md
> 
> 
> Thanks,
> 
> Steven Gill
> 
>

Re: plugman not working on iOS

[Andrew Grieve]

Thanks Anis. I tried as well and wasn't able to get it to fail.

I can make it fail to add frameworks (CB-4993), and fail to prepare (CB-4994),
but I can't get it to fail to add the files so far.


On Wed, Oct 9, 2013 at 7:28 PM, Anis KADRI  wrote:

> I just commented on the issue. It seems like plugman is either not
> invoked or not doing anything and it sounds more like a CLI issue
> since both people are not using plugman directly. I was not able to
> reproduce either way.
>
> On Wed, Oct 9, 2013 at 5:42 AM, Lucas Holmquist 
> wrote:
> > i suppose i should have actually read the comments on the issue :)
> > On Oct 9, 2013, at 8:38 AM, Lucas Holmquist  wrote:
> >
> >> What version of Xcode do you have?
> >>
> >> I will try with the most recent version
> >> On Oct 9, 2013, at 8:35 AM, Andrew Grieve  wrote:
> >>
> >>> Wanted to make sure everyone was aware of CB-4971.
> >>>
> >>> Seems like an emergency-type bug. From what I can tell, plugman is
> silently
> >>> failing to add the Xcode entries for plugin native files.
> >>>
> >>> Anis - I think you may be the most expert at this part? Any clues as to
> >>> what's going on?
> >>
> >
>

Review Request 14566: plugins release - Oct 9, 2013

[Steven Gill]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14566/
---

Review request for cordova.


Repository: cordova-site


Description
---

Added the diff file that has the blog in the bottom.

Also added the .md file as a attachment.


Diffs
-

  /public/blog/index.html 1530831 
  /public/index.html 1530831 
  /public/news/2013/10/01/plugins-release.html 1530831 
  /public/news/2013/10/09/plugins-release-oct-9.html PRE-CREATION 
  /public/news/2013/10/09/plugins-release.html PRE-CREATION 
  /public/rss.xml 1530831 
  /www/_posts/2013-10-01-plugins-release.md 1530831 
  /www/_posts/2013-10-09-plugins-release.md PRE-CREATION 

Diff: https://reviews.apache.org/r/14566/diff/


Testing
---


File Attachments


blog post.md
  
https://reviews.apache.org/media/uploaded/files/2013/10/10/2013-10-09-plugins-release.md


Thanks,

Steven Gill

Re: buildbot failure in Cordova Testing on IOS_Master

[James Jong]

Hi David,
I have a theory but will need to work with your device to test it out.  Let's 
try to get a call on Friday when you can get to the device.
-James Jong

On Oct 9, 2013, at 7:08 PM, David Kemp  wrote:

> 

Re: plugman not working on iOS

[Anis KADRI]

I just commented on the issue. It seems like plugman is either not
invoked or not doing anything and it sounds more like a CLI issue
since both people are not using plugman directly. I was not able to
reproduce either way.

On Wed, Oct 9, 2013 at 5:42 AM, Lucas Holmquist  wrote:
> i suppose i should have actually read the comments on the issue :)
> On Oct 9, 2013, at 8:38 AM, Lucas Holmquist  wrote:
>
>> What version of Xcode do you have?
>>
>> I will try with the most recent version
>> On Oct 9, 2013, at 8:35 AM, Andrew Grieve  wrote:
>>
>>> Wanted to make sure everyone was aware of CB-4971.
>>>
>>> Seems like an emergency-type bug. From what I can tell, plugman is silently
>>> failing to add the Xcode entries for plugin native files.
>>>
>>> Anis - I think you may be the most expert at this part? Any clues as to
>>> what's going on?
>>
>

Re: buildbot failure in Cordova Testing on IOS_Master

[David Kemp]

Hi James,
I had to head out of the office and I am not there tomorrow.
I re-ran the tests just now (remotely) on both master and release just to
check again.
If something went screwy with the device, then the release one should have
a failure too (it was clean)

On release branch, both iPads pass all tests.

On Master Branch, one iPad passes all tests, one failed one test...

6.0 - iPad3,1 failed one test.

I can't give much more detail without pulling the device and running the
tests on a development station.
I can't do that until Friday, but if you don't get anywhere I can do that.

failures0specAccelerometer (navigator.accelerometer) getCurrentAcceleration
accelerometer.spec.5 success callback Acceleration object should return a
rec...
assertions0exceptionExpected 1381359462105.384 to be greater than
1381359462107.trace





On Wed, Oct 9, 2013 at 6:43 PM, James Jong  wrote:

> Thanks Shaz.  Does anyone else have an iOS 6.0 device they can run the
> tests on?
>
> -James Jong
>
> On Oct 9, 2013, at 6:23 PM, Shazron  wrote:
>
> > Just tested on an iPad 3, iOS 7.0.2  with the dev branch of
> > cordova-plugin-device-motion, it passes all tests.
> >
> >
> > On Wed, Oct 9, 2013 at 2:45 PM, Shazron  wrote:
> >
> >> I have an iPad 3 here with 7.0.2 - I'll test and verify soon.
> >>
> >>
> >> On Wed, Oct 9, 2013 at 2:29 PM, James Jong 
> wrote:
> >>
> >>> I'm ok if you want to skip it.  Right now the issue looks like it's
> >>> limited to iPad 3 and/or 6.0.
> >>> -James Jong
> >>>
> >>> On Oct 9, 2013, at 5:23 PM, Steven Gill 
> wrote:
> >>>
>  Should I skip this plugin for today's release until these issues get
> >>> sorted?
> 
> 
>  On Wed, Oct 9, 2013 at 2:01 PM, James Jong 
> >>> wrote:
> 
> > Hmm...   Let me check if I have an iPad at 6.0.  I definitely don't
> >>> have
> > an iPad3 but may have an iPad2.
> >
> > -James Jong
> >
> > On Oct 9, 2013, at 4:53 PM, David Kemp  wrote:
> >
> >>
> >> Hi James,
> >>
> >> That problem went away with the new commit, but now I am getting two
> > failures on one iPad (6.0__iPad3,1)
> >> the other iPad passes all tests (6.1.3 - iPad2,5):
> >>
> >> I tried it twice with the same results.
> >>
> >> failures
> >> 0
> >> spec
> >> Accelerometer (navigator.accelerometer) getCurrentAcceleration
> > accelerometer.spec.5 success callback Acceleration object should
> >>> return a
> > rec...
> >> assertions
> >> 0
> >> exception
> >> timeout: timed out after 7500 msec waiting for win never called
> >> trace
> >> 1
> >> spec
> >> Accelerometer (navigator.accelerometer) watchAcceleration
> > accelerometer.spec.5 success callback Acceleration object should
> >>> return a
> > recent t...
> >> assertions
> >> 0
> >> exception
> >> Expected 1381351391115.972 to be greater than 1381351399373.
> >> trace
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Oct 9, 2013 at 4:36 PM, Andrew Grieve  >
> > wrote:
> >> Awesome!
> >>
> >>
> >> On Wed, Oct 9, 2013 at 4:34 PM, James Jong 
> >>> wrote:
> >>
> >>> Added.
> >>> -James Jong
> >>>
> >>> On Oct 9, 2013, at 4:23 PM, James Jong 
> wrote:
> >>>
>  Ah yes.  Sorry.  I need to add the new framework.
> 
>  -James Jong
> 
>  On Oct 9, 2013, at 4:08 PM, Andrew Grieve 
> > wrote:
> 
> > James - our build bot thinks you broke things! Sadly still
> haven't
> > got
> >>> it exposed, but the error is:
> >
> >
> >
> >
> >>>
> >
> >>>
> /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
> > Undefined symbols for architecture armv7:
> > "_OBJC_CLASS_$_CMMotionManager", referenced from:
> >objc-class-ref in CDVAccelerometer.o
> > ld: symbol(s) not found for architecture armv7
> > clang: error: linker command failed with exit code 1 (use -v to
> see
> >>> invocation)
> >
> >
> > ** BUILD FAILED **
> >
> >
> > The following build commands failed:
> >Ld build/emulator/mobilespec.app/mobilespec normal armv7
> > (1 failure)
> >
> >
> >
> > Likely you need to add CoreMotion to the  of the
> >>> plugin.
> >
> >
> 
> >>>
> >>>
> >>
> >
> >
> >>>
> >>>
> >>
>
>

Re: buildbot failure in Cordova Testing on IOS_Master

[James Jong]

Thanks Shaz.  Does anyone else have an iOS 6.0 device they can run the tests on?

-James Jong

On Oct 9, 2013, at 6:23 PM, Shazron  wrote:

> Just tested on an iPad 3, iOS 7.0.2  with the dev branch of
> cordova-plugin-device-motion, it passes all tests.
> 
> 
> On Wed, Oct 9, 2013 at 2:45 PM, Shazron  wrote:
> 
>> I have an iPad 3 here with 7.0.2 - I'll test and verify soon.
>> 
>> 
>> On Wed, Oct 9, 2013 at 2:29 PM, James Jong  wrote:
>> 
>>> I'm ok if you want to skip it.  Right now the issue looks like it's
>>> limited to iPad 3 and/or 6.0.
>>> -James Jong
>>> 
>>> On Oct 9, 2013, at 5:23 PM, Steven Gill  wrote:
>>> 
 Should I skip this plugin for today's release until these issues get
>>> sorted?
 
 
 On Wed, Oct 9, 2013 at 2:01 PM, James Jong 
>>> wrote:
 
> Hmm...   Let me check if I have an iPad at 6.0.  I definitely don't
>>> have
> an iPad3 but may have an iPad2.
> 
> -James Jong
> 
> On Oct 9, 2013, at 4:53 PM, David Kemp  wrote:
> 
>> 
>> Hi James,
>> 
>> That problem went away with the new commit, but now I am getting two
> failures on one iPad (6.0__iPad3,1)
>> the other iPad passes all tests (6.1.3 - iPad2,5):
>> 
>> I tried it twice with the same results.
>> 
>> failures
>> 0
>> spec
>> Accelerometer (navigator.accelerometer) getCurrentAcceleration
> accelerometer.spec.5 success callback Acceleration object should
>>> return a
> rec...
>> assertions
>> 0
>> exception
>> timeout: timed out after 7500 msec waiting for win never called
>> trace
>> 1
>> spec
>> Accelerometer (navigator.accelerometer) watchAcceleration
> accelerometer.spec.5 success callback Acceleration object should
>>> return a
> recent t...
>> assertions
>> 0
>> exception
>> Expected 1381351391115.972 to be greater than 1381351399373.
>> trace
>> 
>> 
>> 
>> 
>> 
>> On Wed, Oct 9, 2013 at 4:36 PM, Andrew Grieve 
> wrote:
>> Awesome!
>> 
>> 
>> On Wed, Oct 9, 2013 at 4:34 PM, James Jong 
>>> wrote:
>> 
>>> Added.
>>> -James Jong
>>> 
>>> On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
>>> 
 Ah yes.  Sorry.  I need to add the new framework.
 
 -James Jong
 
 On Oct 9, 2013, at 4:08 PM, Andrew Grieve 
> wrote:
 
> James - our build bot thinks you broke things! Sadly still haven't
> got
>>> it exposed, but the error is:
> 
> 
> 
> 
>>> 
> 
>>> /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
> Undefined symbols for architecture armv7:
> "_OBJC_CLASS_$_CMMotionManager", referenced from:
>objc-class-ref in CDVAccelerometer.o
> ld: symbol(s) not found for architecture armv7
> clang: error: linker command failed with exit code 1 (use -v to see
>>> invocation)
> 
> 
> ** BUILD FAILED **
> 
> 
> The following build commands failed:
>Ld build/emulator/mobilespec.app/mobilespec normal armv7
> (1 failure)
> 
> 
> 
> Likely you need to add CoreMotion to the  of the
>>> plugin.
> 
> 
 
>>> 
>>> 
>> 
> 
> 
>>> 
>>> 
>> 

Re: buildbot failure in Cordova Testing on IOS_Master

[Shazron]

Just tested on an iPad 3, iOS 7.0.2  with the dev branch of
cordova-plugin-device-motion, it passes all tests.


On Wed, Oct 9, 2013 at 2:45 PM, Shazron  wrote:

> I have an iPad 3 here with 7.0.2 - I'll test and verify soon.
>
>
> On Wed, Oct 9, 2013 at 2:29 PM, James Jong  wrote:
>
>> I'm ok if you want to skip it.  Right now the issue looks like it's
>> limited to iPad 3 and/or 6.0.
>> -James Jong
>>
>> On Oct 9, 2013, at 5:23 PM, Steven Gill  wrote:
>>
>> > Should I skip this plugin for today's release until these issues get
>> sorted?
>> >
>> >
>> > On Wed, Oct 9, 2013 at 2:01 PM, James Jong 
>> wrote:
>> >
>> >> Hmm...   Let me check if I have an iPad at 6.0.  I definitely don't
>> have
>> >> an iPad3 but may have an iPad2.
>> >>
>> >> -James Jong
>> >>
>> >> On Oct 9, 2013, at 4:53 PM, David Kemp  wrote:
>> >>
>> >>>
>> >>> Hi James,
>> >>>
>> >>> That problem went away with the new commit, but now I am getting two
>> >> failures on one iPad (6.0__iPad3,1)
>> >>> the other iPad passes all tests (6.1.3 - iPad2,5):
>> >>>
>> >>> I tried it twice with the same results.
>> >>>
>> >>> failures
>> >>> 0
>> >>> spec
>> >>> Accelerometer (navigator.accelerometer) getCurrentAcceleration
>> >> accelerometer.spec.5 success callback Acceleration object should
>> return a
>> >> rec...
>> >>> assertions
>> >>> 0
>> >>> exception
>> >>> timeout: timed out after 7500 msec waiting for win never called
>> >>> trace
>> >>> 1
>> >>> spec
>> >>> Accelerometer (navigator.accelerometer) watchAcceleration
>> >> accelerometer.spec.5 success callback Acceleration object should
>> return a
>> >> recent t...
>> >>> assertions
>> >>> 0
>> >>> exception
>> >>> Expected 1381351391115.972 to be greater than 1381351399373.
>> >>> trace
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Wed, Oct 9, 2013 at 4:36 PM, Andrew Grieve 
>> >> wrote:
>> >>> Awesome!
>> >>>
>> >>>
>> >>> On Wed, Oct 9, 2013 at 4:34 PM, James Jong 
>> wrote:
>> >>>
>>  Added.
>>  -James Jong
>> 
>>  On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
>> 
>> > Ah yes.  Sorry.  I need to add the new framework.
>> >
>> > -James Jong
>> >
>> > On Oct 9, 2013, at 4:08 PM, Andrew Grieve 
>> >> wrote:
>> >
>> >> James - our build bot thinks you broke things! Sadly still haven't
>> >> got
>>  it exposed, but the error is:
>> >>
>> >>
>> >>
>> >>
>> 
>> >>
>> /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
>> >> Undefined symbols for architecture armv7:
>> >> "_OBJC_CLASS_$_CMMotionManager", referenced from:
>> >> objc-class-ref in CDVAccelerometer.o
>> >> ld: symbol(s) not found for architecture armv7
>> >> clang: error: linker command failed with exit code 1 (use -v to see
>>  invocation)
>> >>
>> >>
>> >> ** BUILD FAILED **
>> >>
>> >>
>> >> The following build commands failed:
>> >> Ld build/emulator/mobilespec.app/mobilespec normal armv7
>> >> (1 failure)
>> >>
>> >>
>> >>
>> >> Likely you need to add CoreMotion to the  of the
>> plugin.
>> >>
>> >>
>> >
>> 
>> 
>> >>>
>> >>
>> >>
>>
>>
>

Re: buildbot failure in Cordova Testing on IOS_Master

[Shazron]

I have an iPad 3 here with 7.0.2 - I'll test and verify soon.


On Wed, Oct 9, 2013 at 2:29 PM, James Jong  wrote:

> I'm ok if you want to skip it.  Right now the issue looks like it's
> limited to iPad 3 and/or 6.0.
> -James Jong
>
> On Oct 9, 2013, at 5:23 PM, Steven Gill  wrote:
>
> > Should I skip this plugin for today's release until these issues get
> sorted?
> >
> >
> > On Wed, Oct 9, 2013 at 2:01 PM, James Jong  wrote:
> >
> >> Hmm...   Let me check if I have an iPad at 6.0.  I definitely don't have
> >> an iPad3 but may have an iPad2.
> >>
> >> -James Jong
> >>
> >> On Oct 9, 2013, at 4:53 PM, David Kemp  wrote:
> >>
> >>>
> >>> Hi James,
> >>>
> >>> That problem went away with the new commit, but now I am getting two
> >> failures on one iPad (6.0__iPad3,1)
> >>> the other iPad passes all tests (6.1.3 - iPad2,5):
> >>>
> >>> I tried it twice with the same results.
> >>>
> >>> failures
> >>> 0
> >>> spec
> >>> Accelerometer (navigator.accelerometer) getCurrentAcceleration
> >> accelerometer.spec.5 success callback Acceleration object should return
> a
> >> rec...
> >>> assertions
> >>> 0
> >>> exception
> >>> timeout: timed out after 7500 msec waiting for win never called
> >>> trace
> >>> 1
> >>> spec
> >>> Accelerometer (navigator.accelerometer) watchAcceleration
> >> accelerometer.spec.5 success callback Acceleration object should return
> a
> >> recent t...
> >>> assertions
> >>> 0
> >>> exception
> >>> Expected 1381351391115.972 to be greater than 1381351399373.
> >>> trace
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Oct 9, 2013 at 4:36 PM, Andrew Grieve 
> >> wrote:
> >>> Awesome!
> >>>
> >>>
> >>> On Wed, Oct 9, 2013 at 4:34 PM, James Jong 
> wrote:
> >>>
>  Added.
>  -James Jong
> 
>  On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
> 
> > Ah yes.  Sorry.  I need to add the new framework.
> >
> > -James Jong
> >
> > On Oct 9, 2013, at 4:08 PM, Andrew Grieve 
> >> wrote:
> >
> >> James - our build bot thinks you broke things! Sadly still haven't
> >> got
>  it exposed, but the error is:
> >>
> >>
> >>
> >>
> 
> >>
> /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
> >> Undefined symbols for architecture armv7:
> >> "_OBJC_CLASS_$_CMMotionManager", referenced from:
> >> objc-class-ref in CDVAccelerometer.o
> >> ld: symbol(s) not found for architecture armv7
> >> clang: error: linker command failed with exit code 1 (use -v to see
>  invocation)
> >>
> >>
> >> ** BUILD FAILED **
> >>
> >>
> >> The following build commands failed:
> >> Ld build/emulator/mobilespec.app/mobilespec normal armv7
> >> (1 failure)
> >>
> >>
> >>
> >> Likely you need to add CoreMotion to the  of the plugin.
> >>
> >>
> >
> 
> 
> >>>
> >>
> >>
>
>

Re: buildbot failure in Cordova Testing on IOS_Master

[James Jong]

I'm ok if you want to skip it.  Right now the issue looks like it's limited to 
iPad 3 and/or 6.0.
-James Jong

On Oct 9, 2013, at 5:23 PM, Steven Gill  wrote:

> Should I skip this plugin for today's release until these issues get sorted?
> 
> 
> On Wed, Oct 9, 2013 at 2:01 PM, James Jong  wrote:
> 
>> Hmm...   Let me check if I have an iPad at 6.0.  I definitely don't have
>> an iPad3 but may have an iPad2.
>> 
>> -James Jong
>> 
>> On Oct 9, 2013, at 4:53 PM, David Kemp  wrote:
>> 
>>> 
>>> Hi James,
>>> 
>>> That problem went away with the new commit, but now I am getting two
>> failures on one iPad (6.0__iPad3,1)
>>> the other iPad passes all tests (6.1.3 - iPad2,5):
>>> 
>>> I tried it twice with the same results.
>>> 
>>> failures
>>> 0
>>> spec
>>> Accelerometer (navigator.accelerometer) getCurrentAcceleration
>> accelerometer.spec.5 success callback Acceleration object should return a
>> rec...
>>> assertions
>>> 0
>>> exception
>>> timeout: timed out after 7500 msec waiting for win never called
>>> trace
>>> 1
>>> spec
>>> Accelerometer (navigator.accelerometer) watchAcceleration
>> accelerometer.spec.5 success callback Acceleration object should return a
>> recent t...
>>> assertions
>>> 0
>>> exception
>>> Expected 1381351391115.972 to be greater than 1381351399373.
>>> trace
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Wed, Oct 9, 2013 at 4:36 PM, Andrew Grieve 
>> wrote:
>>> Awesome!
>>> 
>>> 
>>> On Wed, Oct 9, 2013 at 4:34 PM, James Jong  wrote:
>>> 
 Added.
 -James Jong
 
 On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
 
> Ah yes.  Sorry.  I need to add the new framework.
> 
> -James Jong
> 
> On Oct 9, 2013, at 4:08 PM, Andrew Grieve 
>> wrote:
> 
>> James - our build bot thinks you broke things! Sadly still haven't
>> got
 it exposed, but the error is:
>> 
>> 
>> 
>> 
 
>> /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
>> Undefined symbols for architecture armv7:
>> "_OBJC_CLASS_$_CMMotionManager", referenced from:
>> objc-class-ref in CDVAccelerometer.o
>> ld: symbol(s) not found for architecture armv7
>> clang: error: linker command failed with exit code 1 (use -v to see
 invocation)
>> 
>> 
>> ** BUILD FAILED **
>> 
>> 
>> The following build commands failed:
>> Ld build/emulator/mobilespec.app/mobilespec normal armv7
>> (1 failure)
>> 
>> 
>> 
>> Likely you need to add CoreMotion to the  of the plugin.
>> 
>> 
> 
 
 
>>> 
>> 
>> 

Re: buildbot failure in Cordova Testing on IOS_Master

[James Jong]

The iPads I have are on 5.1 , 6.1.3 , and 7.  I've just run the tests on each 
of them multiple times and they have passed.

-James Jong

On Oct 9, 2013, at 5:01 PM, James Jong  wrote:

> Hmm...   Let me check if I have an iPad at 6.0.  I definitely don't have an 
> iPad3 but may have an iPad2.
> 
> -James Jong
> 
> On Oct 9, 2013, at 4:53 PM, David Kemp  wrote:
> 
>> 
>> Hi James,
>> 
>> That problem went away with the new commit, but now I am getting two 
>> failures on one iPad (6.0__iPad3,1)
>> the other iPad passes all tests (6.1.3 - iPad2,5):
>> 
>> I tried it twice with the same results.
>> 
>> failures
>> 0
>> spec
>> Accelerometer (navigator.accelerometer) getCurrentAcceleration 
>> accelerometer.spec.5 success callback Acceleration object should return a 
>> rec...
>> assertions
>> 0
>> exception
>> timeout: timed out after 7500 msec waiting for win never called
>> trace
>> 1
>> spec
>> Accelerometer (navigator.accelerometer) watchAcceleration 
>> accelerometer.spec.5 success callback Acceleration object should return a 
>> recent t...
>> assertions
>> 0
>> exception
>> Expected 1381351391115.972 to be greater than 1381351399373.
>> trace
>> 
>> 
>> 
>> 
>> 
>> On Wed, Oct 9, 2013 at 4:36 PM, Andrew Grieve  wrote:
>> Awesome!
>> 
>> 
>> On Wed, Oct 9, 2013 at 4:34 PM, James Jong  wrote:
>> 
>> > Added.
>> > -James Jong
>> >
>> > On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
>> >
>> > > Ah yes.  Sorry.  I need to add the new framework.
>> > >
>> > > -James Jong
>> > >
>> > > On Oct 9, 2013, at 4:08 PM, Andrew Grieve  wrote:
>> > >
>> > >> James - our build bot thinks you broke things! Sadly still haven't got
>> > it exposed, but the error is:
>> > >>
>> > >>
>> > >>
>> > >>
>> > /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
>> > >> Undefined symbols for architecture armv7:
>> > >>  "_OBJC_CLASS_$_CMMotionManager", referenced from:
>> > >>  objc-class-ref in CDVAccelerometer.o
>> > >> ld: symbol(s) not found for architecture armv7
>> > >> clang: error: linker command failed with exit code 1 (use -v to see
>> > invocation)
>> > >>
>> > >>
>> > >> ** BUILD FAILED **
>> > >>
>> > >>
>> > >> The following build commands failed:
>> > >>  Ld build/emulator/mobilespec.app/mobilespec normal armv7
>> > >> (1 failure)
>> > >>
>> > >>
>> > >>
>> > >> Likely you need to add CoreMotion to the  of the plugin.
>> > >>
>> > >>
>> > >
>> >
>> >
>> 
> 

Re: buildbot failure in Cordova Testing on IOS_Master

[Steven Gill]

Should I skip this plugin for today's release until these issues get sorted?


On Wed, Oct 9, 2013 at 2:01 PM, James Jong  wrote:

> Hmm...   Let me check if I have an iPad at 6.0.  I definitely don't have
> an iPad3 but may have an iPad2.
>
> -James Jong
>
> On Oct 9, 2013, at 4:53 PM, David Kemp  wrote:
>
> >
> > Hi James,
> >
> > That problem went away with the new commit, but now I am getting two
> failures on one iPad (6.0__iPad3,1)
> > the other iPad passes all tests (6.1.3 - iPad2,5):
> >
> > I tried it twice with the same results.
> >
> > failures
> > 0
> > spec
> > Accelerometer (navigator.accelerometer) getCurrentAcceleration
> accelerometer.spec.5 success callback Acceleration object should return a
> rec...
> > assertions
> > 0
> > exception
> > timeout: timed out after 7500 msec waiting for win never called
> > trace
> > 1
> > spec
> > Accelerometer (navigator.accelerometer) watchAcceleration
> accelerometer.spec.5 success callback Acceleration object should return a
> recent t...
> > assertions
> > 0
> > exception
> > Expected 1381351391115.972 to be greater than 1381351399373.
> > trace
> >
> >
> >
> >
> >
> > On Wed, Oct 9, 2013 at 4:36 PM, Andrew Grieve 
> wrote:
> > Awesome!
> >
> >
> > On Wed, Oct 9, 2013 at 4:34 PM, James Jong  wrote:
> >
> > > Added.
> > > -James Jong
> > >
> > > On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
> > >
> > > > Ah yes.  Sorry.  I need to add the new framework.
> > > >
> > > > -James Jong
> > > >
> > > > On Oct 9, 2013, at 4:08 PM, Andrew Grieve 
> wrote:
> > > >
> > > >> James - our build bot thinks you broke things! Sadly still haven't
> got
> > > it exposed, but the error is:
> > > >>
> > > >>
> > > >>
> > > >>
> > >
> /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
> > > >> Undefined symbols for architecture armv7:
> > > >>  "_OBJC_CLASS_$_CMMotionManager", referenced from:
> > > >>  objc-class-ref in CDVAccelerometer.o
> > > >> ld: symbol(s) not found for architecture armv7
> > > >> clang: error: linker command failed with exit code 1 (use -v to see
> > > invocation)
> > > >>
> > > >>
> > > >> ** BUILD FAILED **
> > > >>
> > > >>
> > > >> The following build commands failed:
> > > >>  Ld build/emulator/mobilespec.app/mobilespec normal armv7
> > > >> (1 failure)
> > > >>
> > > >>
> > > >>
> > > >> Likely you need to add CoreMotion to the  of the plugin.
> > > >>
> > > >>
> > > >
> > >
> > >
> >
>
>

Re: buildbot failure in Cordova Testing on IOS_Master

[James Jong]

Hmm...   Let me check if I have an iPad at 6.0.  I definitely don't have an 
iPad3 but may have an iPad2.

-James Jong

On Oct 9, 2013, at 4:53 PM, David Kemp  wrote:

> 
> Hi James,
> 
> That problem went away with the new commit, but now I am getting two failures 
> on one iPad (6.0__iPad3,1)
> the other iPad passes all tests (6.1.3 - iPad2,5):
> 
> I tried it twice with the same results.
> 
> failures
> 0
> spec
> Accelerometer (navigator.accelerometer) getCurrentAcceleration 
> accelerometer.spec.5 success callback Acceleration object should return a 
> rec...
> assertions
> 0
> exception
> timeout: timed out after 7500 msec waiting for win never called
> trace
> 1
> spec
> Accelerometer (navigator.accelerometer) watchAcceleration 
> accelerometer.spec.5 success callback Acceleration object should return a 
> recent t...
> assertions
> 0
> exception
> Expected 1381351391115.972 to be greater than 1381351399373.
> trace
> 
> 
> 
> 
> 
> On Wed, Oct 9, 2013 at 4:36 PM, Andrew Grieve  wrote:
> Awesome!
> 
> 
> On Wed, Oct 9, 2013 at 4:34 PM, James Jong  wrote:
> 
> > Added.
> > -James Jong
> >
> > On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
> >
> > > Ah yes.  Sorry.  I need to add the new framework.
> > >
> > > -James Jong
> > >
> > > On Oct 9, 2013, at 4:08 PM, Andrew Grieve  wrote:
> > >
> > >> James - our build bot thinks you broke things! Sadly still haven't got
> > it exposed, but the error is:
> > >>
> > >>
> > >>
> > >>
> > /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
> > >> Undefined symbols for architecture armv7:
> > >>  "_OBJC_CLASS_$_CMMotionManager", referenced from:
> > >>  objc-class-ref in CDVAccelerometer.o
> > >> ld: symbol(s) not found for architecture armv7
> > >> clang: error: linker command failed with exit code 1 (use -v to see
> > invocation)
> > >>
> > >>
> > >> ** BUILD FAILED **
> > >>
> > >>
> > >> The following build commands failed:
> > >>  Ld build/emulator/mobilespec.app/mobilespec normal armv7
> > >> (1 failure)
> > >>
> > >>
> > >>
> > >> Likely you need to add CoreMotion to the  of the plugin.
> > >>
> > >>
> > >
> >
> >
> 

Re: buildbot failure in Cordova Testing on IOS_Master

[David Kemp]

Hi James,

That problem went away with the new commit, but now I am getting two
failures on one iPad (6.0__iPad3,1)
the other iPad passes all tests (6.1.3 - iPad2,5):

I tried it twice with the same results.

failures0specAccelerometer (navigator.accelerometer) getCurrentAcceleration
accelerometer.spec.5 success callback Acceleration object should return a
rec...
assertions0exceptiontimeout: timed out after 7500 msec waiting for win
never calledtrace1specAccelerometer (navigator.accelerometer)
watchAcceleration accelerometer.spec.5 success callback Acceleration object
should return a recent
t...
assertions0exceptionExpected 1381351391115.972 to be greater than
1381351399373.trace





On Wed, Oct 9, 2013 at 4:36 PM, Andrew Grieve  wrote:

> Awesome!
>
>
> On Wed, Oct 9, 2013 at 4:34 PM, James Jong  wrote:
>
> > Added.
> > -James Jong
> >
> > On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
> >
> > > Ah yes.  Sorry.  I need to add the new framework.
> > >
> > > -James Jong
> > >
> > > On Oct 9, 2013, at 4:08 PM, Andrew Grieve 
> wrote:
> > >
> > >> James - our build bot thinks you broke things! Sadly still haven't got
> > it exposed, but the error is:
> > >>
> > >>
> > >>
> > >>
> >
> /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
> > >> Undefined symbols for architecture armv7:
> > >>  "_OBJC_CLASS_$_CMMotionManager", referenced from:
> > >>  objc-class-ref in CDVAccelerometer.o
> > >> ld: symbol(s) not found for architecture armv7
> > >> clang: error: linker command failed with exit code 1 (use -v to see
> > invocation)
> > >>
> > >>
> > >> ** BUILD FAILED **
> > >>
> > >>
> > >> The following build commands failed:
> > >>  Ld build/emulator/mobilespec.app/mobilespec normal armv7
> > >> (1 failure)
> > >>
> > >>
> > >>
> > >> Likely you need to add CoreMotion to the  of the plugin.
> > >>
> > >>
> > >
> >
> >
>

Re: buildbot failure in Cordova Testing on IOS_Master

[James Jong]

Just testing out the new buildbot system ;-)  It works!!
-James Jong

On Oct 9, 2013, at 4:36 PM, Andrew Grieve  wrote:

> Awesome!
> 
> 
> On Wed, Oct 9, 2013 at 4:34 PM, James Jong  wrote:
> Added.
> -James Jong
> 
> On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
> 
> > Ah yes.  Sorry.  I need to add the new framework.
> >
> > -James Jong
> >
> > On Oct 9, 2013, at 4:08 PM, Andrew Grieve  wrote:
> >
> >> James - our build bot thinks you broke things! Sadly still haven't got it 
> >> exposed, but the error is:
> >>
> >>
> >>
> >> /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
> >> Undefined symbols for architecture armv7:
> >>  "_OBJC_CLASS_$_CMMotionManager", referenced from:
> >>  objc-class-ref in CDVAccelerometer.o
> >> ld: symbol(s) not found for architecture armv7
> >> clang: error: linker command failed with exit code 1 (use -v to see 
> >> invocation)
> >>
> >>
> >> ** BUILD FAILED **
> >>
> >>
> >> The following build commands failed:
> >>  Ld build/emulator/mobilespec.app/mobilespec normal armv7
> >> (1 failure)
> >>
> >>
> >>
> >> Likely you need to add CoreMotion to the  of the plugin.
> >>
> >>
> >
> 
> 

Re: buildbot failure in Cordova Testing on IOS_Master

[Andrew Grieve]

Awesome!


On Wed, Oct 9, 2013 at 4:34 PM, James Jong  wrote:

> Added.
> -James Jong
>
> On Oct 9, 2013, at 4:23 PM, James Jong  wrote:
>
> > Ah yes.  Sorry.  I need to add the new framework.
> >
> > -James Jong
> >
> > On Oct 9, 2013, at 4:08 PM, Andrew Grieve  wrote:
> >
> >> James - our build bot thinks you broke things! Sadly still haven't got
> it exposed, but the error is:
> >>
> >>
> >>
> >>
> /Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
> >> Undefined symbols for architecture armv7:
> >>  "_OBJC_CLASS_$_CMMotionManager", referenced from:
> >>  objc-class-ref in CDVAccelerometer.o
> >> ld: symbol(s) not found for architecture armv7
> >> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> >>
> >>
> >> ** BUILD FAILED **
> >>
> >>
> >> The following build commands failed:
> >>  Ld build/emulator/mobilespec.app/mobilespec normal armv7
> >> (1 failure)
> >>
> >>
> >>
> >> Likely you need to add CoreMotion to the  of the plugin.
> >>
> >>
> >
>
>

Re: Plugins Release

[Andrew Grieve]

Btw - sounds good about plugin release!

No need to add the labs plugins (as you said, they are already there), but
it would be good to mention them in your blog post (just the published
ones: keyboard, websql, statusbar).


On Wed, Oct 9, 2013 at 4:32 PM, Andrew Grieve  wrote:

> An alternative to new repos for all of them is to put them in their
> platform repos. So far none of them have multiple platforms.
>
> I'd like to wait a while before creating too many more plugin
> repositories, just until the number of plugins levels out.
>
>
> On Wed, Oct 9, 2013 at 3:32 PM, Steven Gill wrote:
>
>> So plugins that are on cordova-labs will not be included in my release
>> this
>> week.
>>
>> It seems like people have been publishing the cordova-labs plugins
>> independently so far from the (bi)-weekly plugins release.
>>
>> Plugins in cordova-labs include:
>> keyboard (published to registry)
>> websql (published to registry)
>> statusbar (published to registry)
>> file-extras
>> android storage
>>
>> I propose that these plugins (especially the top 3) get moved into repos
>> of
>> their own and join the plugin release train starting with the next
>> release.
>> This way we prevent the plugins branch from becoming another case of
>> https://github.com/phonegap/phonegap-plugins
>>
>> Thoughts?
>>
>> -Steve
>>
>>
>> On Wed, Oct 9, 2013 at 11:24 AM, Steven Gill 
>> wrote:
>>
>> > I am about to initiate the process for doing this release today.
>> >
>> > This will include generating release notes + updating versions for the
>> > plugins that have changes since the last release. I will then publish
>> them
>> > to the registry and whip up a blog post.
>> >
>> > I heard we have more plugins on cordova-labs that could benefit from
>> being
>> > included in this plugins release process. I would love for people to
>> let me
>> > know on this thread what plugins I should be looking at other than our
>> core
>> > ones.
>> >
>> >
>> >
>> >
>> > On Mon, Oct 7, 2013 at 12:37 PM, Steven Gill > >wrote:
>> >
>> >> https://issues.apache.org/jira/browse/CB-5010
>> >>
>> >>
>> >> On Mon, Oct 7, 2013 at 3:24 PM, Steven Gill > >wrote:
>> >>
>> >>> If we want to do CLI/Plugman, we definitely will need to do more
>> testing
>> >>> and fix some things (like FFOS). I think we also need to make sure
>> that
>> >>> some of the changes that went into cordova-3.1.x branches also ended
>> up in
>> >>> the refactored master branches.
>> >>>
>> >>> I will plan on doing the plugins release tomorrow/Wednesday.
>> >>>
>> >>> Steve
>> >>>
>> >>>
>> >>> On Mon, Oct 7, 2013 at 3:16 PM, Andrew Grieve > >wrote:
>> >>>
>>  I remember someone said the refactoring broke ffos. Not sure if
>> that's
>>  fixed yet?
>> 
>>  Other than that, sounds great to release both this week. Would be
>> good
>>  to
>>  do them together so as to have a shared blog post.
>> 
>> 
>>  On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson <
>> bra...@chromium.org
>>  >wrote:
>> 
>>  > Er, I didn't actually say: for the tools, not yet, maybe later this
>>  week.
>>  >
>>  > Braden
>>  >
>>  >
>>  > On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson <
>>  bra...@chromium.org
>>  > >wrote:
>>  >
>>  > > I'll want to have a hand in the next release of the tools,
>> because
>>  of the
>>  > > refactoring.
>>  > >
>>  > > Braden
>>  > >
>>  > >
>>  > > On Mon, Oct 7, 2013 at 2:51 PM, Steven Gill <
>> stevengil...@gmail.com
>>  > >wrote:
>>  > >
>>  > >> Last week as we were finishing off the release, I remember their
>>  was
>>  > some
>>  > >> interest in doing another plugins release this week.
>>  > >>
>>  > >> I know windows 8 file transfer needs to be updated and Shaz has
>>  some iOS
>>  > >> releated plugin changes that could be updated as well.
>>  > >>
>>  > >> Any resistance to me kicking this off and aiming to get out a
>>  plugins
>>  > >> release tomorrow/wed?
>>  > >>
>>  > >> We can also do CLI/Plugman releases on a weekly basis. If anyone
>>  has a
>>  > >> reason to update one of these, let me know and we can kick up a
>>  separate
>>  > >> thread.
>>  > >>
>>  > >> I feel like I got a pretty solid understanding of our various
>>  release
>>  > >> processes over that last two weeks.
>>  > >>
>>  > >> -Steve
>>  > >>
>>  > >
>>  > >
>>  >
>> 
>> >>>
>> >>>
>> >>
>> >
>>
>
>

Re: Plugins Release

[Andrew Grieve]

An alternative to new repos for all of them is to put them in their
platform repos. So far none of them have multiple platforms.

I'd like to wait a while before creating too many more plugin repositories,
just until the number of plugins levels out.


On Wed, Oct 9, 2013 at 3:32 PM, Steven Gill  wrote:

> So plugins that are on cordova-labs will not be included in my release this
> week.
>
> It seems like people have been publishing the cordova-labs plugins
> independently so far from the (bi)-weekly plugins release.
>
> Plugins in cordova-labs include:
> keyboard (published to registry)
> websql (published to registry)
> statusbar (published to registry)
> file-extras
> android storage
>
> I propose that these plugins (especially the top 3) get moved into repos of
> their own and join the plugin release train starting with the next release.
> This way we prevent the plugins branch from becoming another case of
> https://github.com/phonegap/phonegap-plugins
>
> Thoughts?
>
> -Steve
>
>
> On Wed, Oct 9, 2013 at 11:24 AM, Steven Gill 
> wrote:
>
> > I am about to initiate the process for doing this release today.
> >
> > This will include generating release notes + updating versions for the
> > plugins that have changes since the last release. I will then publish
> them
> > to the registry and whip up a blog post.
> >
> > I heard we have more plugins on cordova-labs that could benefit from
> being
> > included in this plugins release process. I would love for people to let
> me
> > know on this thread what plugins I should be looking at other than our
> core
> > ones.
> >
> >
> >
> >
> > On Mon, Oct 7, 2013 at 12:37 PM, Steven Gill  >wrote:
> >
> >> https://issues.apache.org/jira/browse/CB-5010
> >>
> >>
> >> On Mon, Oct 7, 2013 at 3:24 PM, Steven Gill  >wrote:
> >>
> >>> If we want to do CLI/Plugman, we definitely will need to do more
> testing
> >>> and fix some things (like FFOS). I think we also need to make sure that
> >>> some of the changes that went into cordova-3.1.x branches also ended
> up in
> >>> the refactored master branches.
> >>>
> >>> I will plan on doing the plugins release tomorrow/Wednesday.
> >>>
> >>> Steve
> >>>
> >>>
> >>> On Mon, Oct 7, 2013 at 3:16 PM, Andrew Grieve  >wrote:
> >>>
>  I remember someone said the refactoring broke ffos. Not sure if that's
>  fixed yet?
> 
>  Other than that, sounds great to release both this week. Would be good
>  to
>  do them together so as to have a shared blog post.
> 
> 
>  On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson <
> bra...@chromium.org
>  >wrote:
> 
>  > Er, I didn't actually say: for the tools, not yet, maybe later this
>  week.
>  >
>  > Braden
>  >
>  >
>  > On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson <
>  bra...@chromium.org
>  > >wrote:
>  >
>  > > I'll want to have a hand in the next release of the tools, because
>  of the
>  > > refactoring.
>  > >
>  > > Braden
>  > >
>  > >
>  > > On Mon, Oct 7, 2013 at 2:51 PM, Steven Gill <
> stevengil...@gmail.com
>  > >wrote:
>  > >
>  > >> Last week as we were finishing off the release, I remember their
>  was
>  > some
>  > >> interest in doing another plugins release this week.
>  > >>
>  > >> I know windows 8 file transfer needs to be updated and Shaz has
>  some iOS
>  > >> releated plugin changes that could be updated as well.
>  > >>
>  > >> Any resistance to me kicking this off and aiming to get out a
>  plugins
>  > >> release tomorrow/wed?
>  > >>
>  > >> We can also do CLI/Plugman releases on a weekly basis. If anyone
>  has a
>  > >> reason to update one of these, let me know and we can kick up a
>  separate
>  > >> thread.
>  > >>
>  > >> I feel like I got a pretty solid understanding of our various
>  release
>  > >> processes over that last two weeks.
>  > >>
>  > >> -Steve
>  > >>
>  > >
>  > >
>  >
> 
> >>>
> >>>
> >>
> >
>

Fwd: buildbot failure in Cordova Testing on IOS_Master

[Andrew Grieve]

James - our build bot thinks you broke things! Sadly still haven't got it
exposed, but the error is:



/Users/drkemp/buildbot/slave_ios2/IOS_Master/build/mobilespec/platforms/ios/build/emulator/mobilespec.app/mobilespec
Undefined symbols for architecture armv7:
  "_OBJC_CLASS_$_CMMotionManager", referenced from:
  objc-class-ref in CDVAccelerometer.o
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see
invocation)


** BUILD FAILED **


The following build commands failed:
 Ld build/emulator/mobilespec.app/mobilespec normal armv7
(1 failure)



Likely you need to add CoreMotion to the  of the plugin.

Re: Plugins Release

[Steven Gill]

So plugins that are on cordova-labs will not be included in my release this
week.

It seems like people have been publishing the cordova-labs plugins
independently so far from the (bi)-weekly plugins release.

Plugins in cordova-labs include:
keyboard (published to registry)
websql (published to registry)
statusbar (published to registry)
file-extras
android storage

I propose that these plugins (especially the top 3) get moved into repos of
their own and join the plugin release train starting with the next release.
This way we prevent the plugins branch from becoming another case of
https://github.com/phonegap/phonegap-plugins

Thoughts?

-Steve


On Wed, Oct 9, 2013 at 11:24 AM, Steven Gill  wrote:

> I am about to initiate the process for doing this release today.
>
> This will include generating release notes + updating versions for the
> plugins that have changes since the last release. I will then publish them
> to the registry and whip up a blog post.
>
> I heard we have more plugins on cordova-labs that could benefit from being
> included in this plugins release process. I would love for people to let me
> know on this thread what plugins I should be looking at other than our core
> ones.
>
>
>
>
> On Mon, Oct 7, 2013 at 12:37 PM, Steven Gill wrote:
>
>> https://issues.apache.org/jira/browse/CB-5010
>>
>>
>> On Mon, Oct 7, 2013 at 3:24 PM, Steven Gill wrote:
>>
>>> If we want to do CLI/Plugman, we definitely will need to do more testing
>>> and fix some things (like FFOS). I think we also need to make sure that
>>> some of the changes that went into cordova-3.1.x branches also ended up in
>>> the refactored master branches.
>>>
>>> I will plan on doing the plugins release tomorrow/Wednesday.
>>>
>>> Steve
>>>
>>>
>>> On Mon, Oct 7, 2013 at 3:16 PM, Andrew Grieve wrote:
>>>
 I remember someone said the refactoring broke ffos. Not sure if that's
 fixed yet?

 Other than that, sounds great to release both this week. Would be good
 to
 do them together so as to have a shared blog post.


 On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson >>> >wrote:

 > Er, I didn't actually say: for the tools, not yet, maybe later this
 week.
 >
 > Braden
 >
 >
 > On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson <
 bra...@chromium.org
 > >wrote:
 >
 > > I'll want to have a hand in the next release of the tools, because
 of the
 > > refactoring.
 > >
 > > Braden
 > >
 > >
 > > On Mon, Oct 7, 2013 at 2:51 PM, Steven Gill >>> > >wrote:
 > >
 > >> Last week as we were finishing off the release, I remember their
 was
 > some
 > >> interest in doing another plugins release this week.
 > >>
 > >> I know windows 8 file transfer needs to be updated and Shaz has
 some iOS
 > >> releated plugin changes that could be updated as well.
 > >>
 > >> Any resistance to me kicking this off and aiming to get out a
 plugins
 > >> release tomorrow/wed?
 > >>
 > >> We can also do CLI/Plugman releases on a weekly basis. If anyone
 has a
 > >> reason to update one of these, let me know and we can kick up a
 separate
 > >> thread.
 > >>
 > >> I feel like I got a pretty solid understanding of our various
 release
 > >> processes over that last two weeks.
 > >>
 > >> -Steve
 > >>
 > >
 > >
 >

>>>
>>>
>>
>

Re: Plugins Release

[Steven Gill]

I am about to initiate the process for doing this release today.

This will include generating release notes + updating versions for the
plugins that have changes since the last release. I will then publish them
to the registry and whip up a blog post.

I heard we have more plugins on cordova-labs that could benefit from being
included in this plugins release process. I would love for people to let me
know on this thread what plugins I should be looking at other than our core
ones.




On Mon, Oct 7, 2013 at 12:37 PM, Steven Gill  wrote:

> https://issues.apache.org/jira/browse/CB-5010
>
>
> On Mon, Oct 7, 2013 at 3:24 PM, Steven Gill wrote:
>
>> If we want to do CLI/Plugman, we definitely will need to do more testing
>> and fix some things (like FFOS). I think we also need to make sure that
>> some of the changes that went into cordova-3.1.x branches also ended up in
>> the refactored master branches.
>>
>> I will plan on doing the plugins release tomorrow/Wednesday.
>>
>> Steve
>>
>>
>> On Mon, Oct 7, 2013 at 3:16 PM, Andrew Grieve wrote:
>>
>>> I remember someone said the refactoring broke ffos. Not sure if that's
>>> fixed yet?
>>>
>>> Other than that, sounds great to release both this week. Would be good to
>>> do them together so as to have a shared blog post.
>>>
>>>
>>> On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson >> >wrote:
>>>
>>> > Er, I didn't actually say: for the tools, not yet, maybe later this
>>> week.
>>> >
>>> > Braden
>>> >
>>> >
>>> > On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson <
>>> bra...@chromium.org
>>> > >wrote:
>>> >
>>> > > I'll want to have a hand in the next release of the tools, because
>>> of the
>>> > > refactoring.
>>> > >
>>> > > Braden
>>> > >
>>> > >
>>> > > On Mon, Oct 7, 2013 at 2:51 PM, Steven Gill >> > >wrote:
>>> > >
>>> > >> Last week as we were finishing off the release, I remember their was
>>> > some
>>> > >> interest in doing another plugins release this week.
>>> > >>
>>> > >> I know windows 8 file transfer needs to be updated and Shaz has
>>> some iOS
>>> > >> releated plugin changes that could be updated as well.
>>> > >>
>>> > >> Any resistance to me kicking this off and aiming to get out a
>>> plugins
>>> > >> release tomorrow/wed?
>>> > >>
>>> > >> We can also do CLI/Plugman releases on a weekly basis. If anyone
>>> has a
>>> > >> reason to update one of these, let me know and we can kick up a
>>> separate
>>> > >> thread.
>>> > >>
>>> > >> I feel like I got a pretty solid understanding of our various
>>> release
>>> > >> processes over that last two weeks.
>>> > >>
>>> > >> -Steve
>>> > >>
>>> > >
>>> > >
>>> >
>>>
>>
>>
>

Re: [iOS] Moving setting of UIWebView properties to its own plugin from the core

[Shazron]

If we do that, might as well pluginize (well its already a plugin) the
CDVLocalStorage stuff as well into that process. But! The difference in the
CDVLocalStorage plugin is, it has to be loaded/run before the UIWebView is
created, so I don't think it would work (unless we have another feature
param attribute, or something)


On Wed, Oct 9, 2013 at 9:47 AM, Andrew Grieve  wrote:

> I think pluginerizing the settings is a good idea. A nice-to-have here
> would be to have the plugin installed by default for new projects. Maybe we
> can ship a version of the plugin with platforms, and then allow it to be
> upgraded via the registry?
>
>
> On Wed, Oct 9, 2013 at 11:43 AM, Brian LeRoux  wrote:
>
> > I am all in favor of distilling platforms down to the very essence and
> > 'plugin all the things'. Way easier for issue tracking, maintenance, and
> > upgrading.
> >
> >
> > On Wed, Oct 9, 2013 at 7:23 AM, Shazron  wrote:
> >
> > > See: https://issues.apache.org/jira/browse/CB-5026
> > >
> > >
> > > Pros:
> > > - if iOS >= 8 adds more properties, and people want to stick to Cordova
> > 3.A
> > > and we only support it in 3.B or 4.x, they only have to update a plugin
> > and
> > > not the whole core.
> > >
> > > Cons:
> > > - if they rely on these settings, they will lose them when they upgrade
> > if
> > > they don't install a plugin, this won't be any different when they
> moved
> > > from 2.x to 3.x
> > > - Yet Another Repo?
> > >
> >
>

Re: [iOS] Moving setting of UIWebView properties to its own plugin from the core

[Michal Mocny]

Or support optional-plugin-dependencies for platforms for 3.2?  This has
come up before for the console plugin for ios..


On Wed, Oct 9, 2013 at 12:47 PM, Andrew Grieve  wrote:

> I think pluginerizing the settings is a good idea. A nice-to-have here
> would be to have the plugin installed by default for new projects. Maybe we
> can ship a version of the plugin with platforms, and then allow it to be
> upgraded via the registry?
>
>
> On Wed, Oct 9, 2013 at 11:43 AM, Brian LeRoux  wrote:
>
> > I am all in favor of distilling platforms down to the very essence and
> > 'plugin all the things'. Way easier for issue tracking, maintenance, and
> > upgrading.
> >
> >
> > On Wed, Oct 9, 2013 at 7:23 AM, Shazron  wrote:
> >
> > > See: https://issues.apache.org/jira/browse/CB-5026
> > >
> > >
> > > Pros:
> > > - if iOS >= 8 adds more properties, and people want to stick to Cordova
> > 3.A
> > > and we only support it in 3.B or 4.x, they only have to update a plugin
> > and
> > > not the whole core.
> > >
> > > Cons:
> > > - if they rely on these settings, they will lose them when they upgrade
> > if
> > > they don't install a plugin, this won't be any different when they
> moved
> > > from 2.x to 3.x
> > > - Yet Another Repo?
> > >
> >
>

Re: [iOS] Moving setting of UIWebView properties to its own plugin from the core

[Andrew Grieve]

I think pluginerizing the settings is a good idea. A nice-to-have here
would be to have the plugin installed by default for new projects. Maybe we
can ship a version of the plugin with platforms, and then allow it to be
upgraded via the registry?


On Wed, Oct 9, 2013 at 11:43 AM, Brian LeRoux  wrote:

> I am all in favor of distilling platforms down to the very essence and
> 'plugin all the things'. Way easier for issue tracking, maintenance, and
> upgrading.
>
>
> On Wed, Oct 9, 2013 at 7:23 AM, Shazron  wrote:
>
> > See: https://issues.apache.org/jira/browse/CB-5026
> >
> >
> > Pros:
> > - if iOS >= 8 adds more properties, and people want to stick to Cordova
> 3.A
> > and we only support it in 3.B or 4.x, they only have to update a plugin
> and
> > not the whole core.
> >
> > Cons:
> > - if they rely on these settings, they will lose them when they upgrade
> if
> > they don't install a plugin, this won't be any different when they moved
> > from 2.x to 3.x
> > - Yet Another Repo?
> >
>

Re: Platforms Meet-up @ Waterloo

[Bryan Higgins]

Great idea. I'll be there!


On Wed, Oct 9, 2013 at 11:47 AM, Shazron  wrote:

> +1 will be there!
>
>
> On Wed, Oct 9, 2013 at 7:10 AM, Andrew Grieve 
> wrote:
>
> > Working via email is fun, but seeing each other in person is fun too!
> >
> > I'd like to invite committers / active contributors who are able to join
> > the Google team for a couple days of work and fun at the Google Waterloo
> > office!
> >
> > When: Oct 29th, 30th (Tuesday, Wednesday)
> > Where: Google Waterloo (http://goo.gl/jI99Fr)
> > Full Address: 151 Charles Street West, Kitchener, Ontario
> > What: Working together + dinner and a social activity evening of the 29th
> >
> > More details:
> > A lot of focus recently has been on CLI/Plugman, so I wanted this meet-up
> > to instead focus on *platforms*.
> >
> > Specifically:
> > - iOS & Android Roadmaps (other platforms too depending on who's
> attending)
> > - Storage locations (CB-285) (oldie but a goldie!)
> > - Accessibility (both IBM and Adobe have mentioned this recently, not
> sure
> > if there's anything to share / report yet)
> >
> > If you're able to come, please respond to this thread so I can get an
> idea
> > of numbers. We'll provide food and a work space, but you'll have to
> figure
> > out how to get here. As always, we'll be sure to not make any decisions
> > without going through the ML.
> >
> > Andrew
> >
>

Re: Platforms Meet-up @ Waterloo

[Shazron]

+1 will be there!


On Wed, Oct 9, 2013 at 7:10 AM, Andrew Grieve  wrote:

> Working via email is fun, but seeing each other in person is fun too!
>
> I'd like to invite committers / active contributors who are able to join
> the Google team for a couple days of work and fun at the Google Waterloo
> office!
>
> When: Oct 29th, 30th (Tuesday, Wednesday)
> Where: Google Waterloo (http://goo.gl/jI99Fr)
> Full Address: 151 Charles Street West, Kitchener, Ontario
> What: Working together + dinner and a social activity evening of the 29th
>
> More details:
> A lot of focus recently has been on CLI/Plugman, so I wanted this meet-up
> to instead focus on *platforms*.
>
> Specifically:
> - iOS & Android Roadmaps (other platforms too depending on who's attending)
> - Storage locations (CB-285) (oldie but a goldie!)
> - Accessibility (both IBM and Adobe have mentioned this recently, not sure
> if there's anything to share / report yet)
>
> If you're able to come, please respond to this thread so I can get an idea
> of numbers. We'll provide food and a work space, but you'll have to figure
> out how to get here. As always, we'll be sure to not make any decisions
> without going through the ML.
>
> Andrew
>

Re: So, what to do about storage issues?

[Joe Bowser]

I think this is the namespace issue.  We need to make sure the plugin
always overrides the default namespace.
On Oct 9, 2013 8:00 AM, "Andrew Grieve"  wrote:

> Example project would be great!
>
>
> On Wed, Oct 9, 2013 at 10:27 AM, Dick Van den Brink <
> d_vandenbr...@outlook.com> wrote:
>
> > I don't think it is fixed with the org.apache.cordova.websql plugin.I
> > still can open only one database. The second one is giving me a security
> > error on Android 4.1.2.
> > I'm on Cordova 3.0 btw. I added some logging to the websql plugin code to
> > make sure it was using it and that seems to be the case. I can create an
> > example project if you want.
> >
> > > From: agri...@chromium.org
> > > Date: Wed, 9 Oct 2013 10:04:14 -0400
> > > Subject: Re: So, what to do about storage issues?
> > > To: dev@cordova.apache.org
> > >
> > > I think let's document the quirks (CB-4760), and close the other two as
> > > fixed (via org.apache.cordova.websql plugin)
> > >
> > >
> > > On Tue, Oct 8, 2013 at 5:55 PM, Shazron  wrote:
> > >
> > > > Not sure you guys got Ray's message below if you were on Gmail --
> > since it
> > > > filtered it out as spam (confirmed with another committer/Gmail user)
> > :/
> > > >
> > > >
> > > > On Tue, Oct 8, 2013 at 2:30 PM, Ray Camden 
> wrote:
> > > >
> > > > > Hmm, from CB-4760:
> > > > >
> > > > > "The problem is that the Storage Guide documentation
> > > > > (
> > > > >
> > > >
> >
> http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#St
> > > > > orage) currently doesn't mention any Android Quirks at all, so as
> > far as
> > > > > user knows it should all work OK as per the API guide."
> > > > >
> > > > > Yeah - this is what worries me the most. Couldn't the docs be
> updated
> > > > > pretty quickly to let folks know about issues?
> > > > >
> > > > >
> > > > > On 10/8/13 4:05 PM, "Joe Bowser"  wrote:
> > > > >
> > > > > >What should we do for Storage Plugin issues on Android? Should we
> > just
> > > > > >close them as "Won't Fix" and tell people to use the cordova-labs
> > > > > >plugins?  Currently, we don't have a plugin repo for the storage
> > > > > >plugin, and it's been ripped out in 3.x.
> > > > > >
> > > > > >What should we do with these issues??
> > > > > >https://issues.apache.org/jira/browse/CB-4506
> > > > > >https://issues.apache.org/jira/browse/CB-4505
> > > > > >https://issues.apache.org/jira/browse/CB-4760
> > > > > >
> > > > > >Thoughts?
> > > > > >
> > > > > >Joe
> > > > >
> > > > >
> > > >
> >
> >
>

Re: [iOS] Moving setting of UIWebView properties to its own plugin from the core

[Brian LeRoux]

I am all in favor of distilling platforms down to the very essence and
'plugin all the things'. Way easier for issue tracking, maintenance, and
upgrading.


On Wed, Oct 9, 2013 at 7:23 AM, Shazron  wrote:

> See: https://issues.apache.org/jira/browse/CB-5026
>
>
> Pros:
> - if iOS >= 8 adds more properties, and people want to stick to Cordova 3.A
> and we only support it in 3.B or 4.x, they only have to update a plugin and
> not the whole core.
>
> Cons:
> - if they rely on these settings, they will lose them when they upgrade if
> they don't install a plugin, this won't be any different when they moved
> from 2.x to 3.x
> - Yet Another Repo?
>

Re: So, what to do about storage issues?

[Andrew Grieve]

Example project would be great!


On Wed, Oct 9, 2013 at 10:27 AM, Dick Van den Brink <
d_vandenbr...@outlook.com> wrote:

> I don't think it is fixed with the org.apache.cordova.websql plugin.I
> still can open only one database. The second one is giving me a security
> error on Android 4.1.2.
> I'm on Cordova 3.0 btw. I added some logging to the websql plugin code to
> make sure it was using it and that seems to be the case. I can create an
> example project if you want.
>
> > From: agri...@chromium.org
> > Date: Wed, 9 Oct 2013 10:04:14 -0400
> > Subject: Re: So, what to do about storage issues?
> > To: dev@cordova.apache.org
> >
> > I think let's document the quirks (CB-4760), and close the other two as
> > fixed (via org.apache.cordova.websql plugin)
> >
> >
> > On Tue, Oct 8, 2013 at 5:55 PM, Shazron  wrote:
> >
> > > Not sure you guys got Ray's message below if you were on Gmail --
> since it
> > > filtered it out as spam (confirmed with another committer/Gmail user)
> :/
> > >
> > >
> > > On Tue, Oct 8, 2013 at 2:30 PM, Ray Camden  wrote:
> > >
> > > > Hmm, from CB-4760:
> > > >
> > > > "The problem is that the Storage Guide documentation
> > > > (
> > > >
> > >
> http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#St
> > > > orage) currently doesn't mention any Android Quirks at all, so as
> far as
> > > > user knows it should all work OK as per the API guide."
> > > >
> > > > Yeah - this is what worries me the most. Couldn't the docs be updated
> > > > pretty quickly to let folks know about issues?
> > > >
> > > >
> > > > On 10/8/13 4:05 PM, "Joe Bowser"  wrote:
> > > >
> > > > >What should we do for Storage Plugin issues on Android? Should we
> just
> > > > >close them as "Won't Fix" and tell people to use the cordova-labs
> > > > >plugins?  Currently, we don't have a plugin repo for the storage
> > > > >plugin, and it's been ripped out in 3.x.
> > > > >
> > > > >What should we do with these issues??
> > > > >https://issues.apache.org/jira/browse/CB-4506
> > > > >https://issues.apache.org/jira/browse/CB-4505
> > > > >https://issues.apache.org/jira/browse/CB-4760
> > > > >
> > > > >Thoughts?
> > > > >
> > > > >Joe
> > > >
> > > >
> > >
>
>

RE: So, what to do about storage issues?

[Dick Van den Brink]

I don't think it is fixed with the org.apache.cordova.websql plugin.I still can 
open only one database. The second one is giving me a security error on Android 
4.1.2.
I'm on Cordova 3.0 btw. I added some logging to the websql plugin code to make 
sure it was using it and that seems to be the case. I can create an example 
project if you want.

> From: agri...@chromium.org
> Date: Wed, 9 Oct 2013 10:04:14 -0400
> Subject: Re: So, what to do about storage issues?
> To: dev@cordova.apache.org
> 
> I think let's document the quirks (CB-4760), and close the other two as
> fixed (via org.apache.cordova.websql plugin)
> 
> 
> On Tue, Oct 8, 2013 at 5:55 PM, Shazron  wrote:
> 
> > Not sure you guys got Ray's message below if you were on Gmail -- since it
> > filtered it out as spam (confirmed with another committer/Gmail user) :/
> >
> >
> > On Tue, Oct 8, 2013 at 2:30 PM, Ray Camden  wrote:
> >
> > > Hmm, from CB-4760:
> > >
> > > "The problem is that the Storage Guide documentation
> > > (
> > >
> > http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#St
> > > orage) currently doesn't mention any Android Quirks at all, so as far as
> > > user knows it should all work OK as per the API guide."
> > >
> > > Yeah - this is what worries me the most. Couldn't the docs be updated
> > > pretty quickly to let folks know about issues?
> > >
> > >
> > > On 10/8/13 4:05 PM, "Joe Bowser"  wrote:
> > >
> > > >What should we do for Storage Plugin issues on Android? Should we just
> > > >close them as "Won't Fix" and tell people to use the cordova-labs
> > > >plugins?  Currently, we don't have a plugin repo for the storage
> > > >plugin, and it's been ripped out in 3.x.
> > > >
> > > >What should we do with these issues??
> > > >https://issues.apache.org/jira/browse/CB-4506
> > > >https://issues.apache.org/jira/browse/CB-4505
> > > >https://issues.apache.org/jira/browse/CB-4760
> > > >
> > > >Thoughts?
> > > >
> > > >Joe
> > >
> > >
> >
  

[iOS] Moving setting of UIWebView properties to its own plugin from the core

[Shazron]

See: https://issues.apache.org/jira/browse/CB-5026


Pros:
- if iOS >= 8 adds more properties, and people want to stick to Cordova 3.A
and we only support it in 3.B or 4.x, they only have to update a plugin and
not the whole core.

Cons:
- if they rely on these settings, they will lose them when they upgrade if
they don't install a plugin, this won't be any different when they moved
from 2.x to 3.x
- Yet Another Repo?

Platforms Meet-up @ Waterloo

[Andrew Grieve]

Working via email is fun, but seeing each other in person is fun too!

I'd like to invite committers / active contributors who are able to join
the Google team for a couple days of work and fun at the Google Waterloo
office!

When: Oct 29th, 30th (Tuesday, Wednesday)
Where: Google Waterloo (http://goo.gl/jI99Fr)
Full Address: 151 Charles Street West, Kitchener, Ontario
What: Working together + dinner and a social activity evening of the 29th

More details:
A lot of focus recently has been on CLI/Plugman, so I wanted this meet-up
to instead focus on *platforms*.

Specifically:
- iOS & Android Roadmaps (other platforms too depending on who's attending)
- Storage locations (CB-285) (oldie but a goldie!)
- Accessibility (both IBM and Adobe have mentioned this recently, not sure
if there's anything to share / report yet)

If you're able to come, please respond to this thread so I can get an idea
of numbers. We'll provide food and a work space, but you'll have to figure
out how to get here. As always, we'll be sure to not make any decisions
without going through the ML.

Andrew

Re: So, what to do about storage issues?

[Andrew Grieve]

I think let's document the quirks (CB-4760), and close the other two as
fixed (via org.apache.cordova.websql plugin)


On Tue, Oct 8, 2013 at 5:55 PM, Shazron  wrote:

> Not sure you guys got Ray's message below if you were on Gmail -- since it
> filtered it out as spam (confirmed with another committer/Gmail user) :/
>
>
> On Tue, Oct 8, 2013 at 2:30 PM, Ray Camden  wrote:
>
> > Hmm, from CB-4760:
> >
> > "The problem is that the Storage Guide documentation
> > (
> >
> http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#St
> > orage) currently doesn't mention any Android Quirks at all, so as far as
> > user knows it should all work OK as per the API guide."
> >
> > Yeah - this is what worries me the most. Couldn't the docs be updated
> > pretty quickly to let folks know about issues?
> >
> >
> > On 10/8/13 4:05 PM, "Joe Bowser"  wrote:
> >
> > >What should we do for Storage Plugin issues on Android? Should we just
> > >close them as "Won't Fix" and tell people to use the cordova-labs
> > >plugins?  Currently, we don't have a plugin repo for the storage
> > >plugin, and it's been ripped out in 3.x.
> > >
> > >What should we do with these issues??
> > >https://issues.apache.org/jira/browse/CB-4506
> > >https://issues.apache.org/jira/browse/CB-4505
> > >https://issues.apache.org/jira/browse/CB-4760
> > >
> > >Thoughts?
> > >
> > >Joe
> >
> >
>

Re: plugman not working on iOS

[Lucas Holmquist]

i suppose i should have actually read the comments on the issue :)
On Oct 9, 2013, at 8:38 AM, Lucas Holmquist  wrote:

> What version of Xcode do you have? 
> 
> I will try with the most recent version
> On Oct 9, 2013, at 8:35 AM, Andrew Grieve  wrote:
> 
>> Wanted to make sure everyone was aware of CB-4971.
>> 
>> Seems like an emergency-type bug. From what I can tell, plugman is silently
>> failing to add the Xcode entries for plugin native files.
>> 
>> Anis - I think you may be the most expert at this part? Any clues as to
>> what's going on?
> 

Re: plugman not working on iOS

[Lucas Holmquist]

What version of Xcode do you have? 

I will try with the most recent version
On Oct 9, 2013, at 8:35 AM, Andrew Grieve  wrote:

> Wanted to make sure everyone was aware of CB-4971.
> 
> Seems like an emergency-type bug. From what I can tell, plugman is silently
> failing to add the Xcode entries for plugin native files.
> 
> Anis - I think you may be the most expert at this part? Any clues as to
> what's going on?

plugman not working on iOS

[Andrew Grieve]

Wanted to make sure everyone was aware of CB-4971.

Seems like an emergency-type bug. From what I can tell, plugman is silently
failing to add the Xcode entries for plugin native files.

Anis - I think you may be the most expert at this part? Any clues as to
what's going on?