bump
With the release, its been a bit busy, but this issue needs some love.
Note that someone else has commented on the same problem from a different
angle (not mobilespec)
[Commented] (CB-4889) ~ 3am this morning
The renaming of plugins created a hole and there are a couple possible
I'm fine with any of the options.
On Thu, Oct 3, 2013 at 1:47 PM, David Kemp drk...@google.com wrote:
bump
With the release, its been a bit busy, but this issue needs some love.
Note that someone else has commented on the same problem from a different
angle (not mobilespec)
On Thu, Oct 3, 2013 at 8:47 AM, David Kemp drk...@google.com wrote:
bump
With the release, its been a bit busy, but this issue needs some love.
Note that someone else has commented on the same problem from a different
angle (not mobilespec)
[Commented] (CB-4889) ~ 3am this morning
Summary: Due to the renaming of plugins, there is no longer a sensible way
to test 3.0.x
Detail:
The process to test 3.0.x is to get platforms, mobile-spec, etc from 3.0.x
and plugins from master. With the change on plugin names (remove core) the
3.0.x mobile-spec still refers to the names with
In the past I've used #3. When checking out code to test, I try to get all the
assets from the same branch / time period. But I may be skewed in that
approach, since our product that embeds Cordova has a snapshot of the platforms
and plugins, and doesn't get updates from the online repos.
Does
The issue is the that stated methodology for getting the right versions to
test is:
* for release, get plugins from the master branch and platforms, tests etc
from the release branch (3.0.x)
* for tip of tree, get plugins from the dev branch and platforms, tests etc
from the master branch
Since
Would it fix it to use mobile-spec from master when testing 3.0.x?
Mobile-spec generally stays in sync with the plugins more so than the
platforms, so it would make sense to me to use mobile-spec at master if
using plugins from master/dev.
On Tue, Oct 1, 2013 at 4:40 PM, David Kemp
I believe that will be OK - testing it out now.
It still probably deserves some documentation somewhere that the previously
stated relationships don't work anymore, and that any plugin references in
a 3.0.x project need attention.
On Tue, Oct 1, 2013 at 12:03 PM, Andrew Grieve
I am running regression tests on 3.0.x as well as tests on the tip of tree.
I have not yet switched to running regression on 3.1.x since it isn't
actually released yet.
The problem is that suddenly the 3.0.x tests fail. This is mostly because
the plugins are not tied to a release, but mobilespec
In answer to Andrews response, there was a problem with 3.0.x where the
echo plugin was mostly removed, but the two source files CDVEcho.m,
CDVEcho.h were left in iOS core. When you build 3.0.x with the master
version (or 3.1.x) of Mobilespec and it includes the new Echo plugin, you
get duplicate
Just for clarification...
Testing 3.1.x works fine using 3.1 platforms, 3.1 mobilespec, and master
plugins.
Testing 'HEAD' works fine using master platforms, master mobilespec, and
dev plugins.
Thats all as expected.
Up until a week ago, you could test 3.0.x using 3.0.x platforms, 3.0.x
11 matches
Mail list logo
