[jira] [Commented] (CB-6205) Platform Support Docs plugin links not found
[ https://issues.apache.org/jira/browse/CB-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925363#comment-13925363 ] Angela Fowler commented on CB-6205: --- To give some examples : The plugin release news http://cordova.apache.org/news/2014/03/03/plugins-release.html lists org.apache.cordova.camera@0.2.8 but on github the latest tag is https://github.com/apache/cordova-plugin-camera/tree/r0.2.7 and registry http://plugins.cordova.io/#/org.apache.cordova.camera has 0.2.8 The news lists org.apache.cordova.inappbrowser@0.3.2 but on github and registry 0.3.3 https://github.com/apache/cordova-plugin-inappbrowser/tree/r0.3.3 and registry http://plugins.cordova.io/#/org.apache.cordova.inappbrowser has 0.3.3 > Platform Support Docs plugin links not found > > > Key: CB-6205 > URL: https://issues.apache.org/jira/browse/CB-6205 > Project: Apache Cordova > Issue Type: Bug > Components: Docs, Plugins >Affects Versions: 3.2.0, 3.3.0, 3.4.0 >Reporter: Angela Fowler >Priority: Minor > > http://cordova.apache.org/docs/en/3.4.0/guide_support_index.md.html#Platform%20Support > The links to plugin docs are broken. > e.g. > http://cordova.apache.org/docs/en/3.4.0/cordova_accelerometer_accelerometer.md.html > Is there a summary in one place of which plugin versions have been tested > with a Cordova version? e.g. org.apache.cordova.camera@0.2.8 was released > last week but accelerometer in a previous release. > Would the platform support page be a good place to add this information? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5258) build / run - stdout & stderr empty on Windows
[ https://issues.apache.org/jira/browse/CB-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925359#comment-13925359 ] Jonathan Bond commented on CB-5258: --- Looks like is this fixed is node: https://github.com/joyent/node/commit/20176a98416353d4596900793f739d5ebf4f0ee1 > build / run - stdout & stderr empty on Windows > -- > > Key: CB-5258 > URL: https://issues.apache.org/jira/browse/CB-5258 > Project: Apache Cordova > Issue Type: Bug > Components: Android, BlackBerry, CLI, Coho, iOS, Plugman >Affects Versions: 3.1.0 >Reporter: Bryan Higgins >Assignee: Josh Soref > Fix For: 3.5.0 > > > Cordova CLI build and run commands do not show any error messages (stderr) > and when running in verbose mode no script output is displayed (stdout). > I noticed this problem testing Windows 8 + BlackBerry. I'm not sure if it > also affects other platforms. > Reverting from spawn to exec does not appear to fix the issue. Nor does > removing the call to "cmd /C" and appending ".bat". -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CB-5258) build / run - stdout & stderr empty on Windows
[ https://issues.apache.org/jira/browse/CB-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925359#comment-13925359 ] Jonathan Bond edited comment on CB-5258 at 3/9/14 11:36 PM: Looks like this is fixed in node: https://github.com/joyent/node/commit/20176a98416353d4596900793f739d5ebf4f0ee1 was (Author: jbondc): Looks like is this fixed is node: https://github.com/joyent/node/commit/20176a98416353d4596900793f739d5ebf4f0ee1 > build / run - stdout & stderr empty on Windows > -- > > Key: CB-5258 > URL: https://issues.apache.org/jira/browse/CB-5258 > Project: Apache Cordova > Issue Type: Bug > Components: Android, BlackBerry, CLI, Coho, iOS, Plugman >Affects Versions: 3.1.0 >Reporter: Bryan Higgins >Assignee: Josh Soref > Fix For: 3.5.0 > > > Cordova CLI build and run commands do not show any error messages (stderr) > and when running in verbose mode no script output is displayed (stdout). > I noticed this problem testing Windows 8 + BlackBerry. I'm not sure if it > also affects other platforms. > Reverting from spawn to exec does not appear to fix the issue. Nor does > removing the call to "cmd /C" and appending ".bat". -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6205) Platform Support Docs plugin links not found
Angela Fowler created CB-6205: - Summary: Platform Support Docs plugin links not found Key: CB-6205 URL: https://issues.apache.org/jira/browse/CB-6205 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugins Affects Versions: 3.4.0, 3.3.0, 3.2.0 Reporter: Angela Fowler Priority: Minor http://cordova.apache.org/docs/en/3.4.0/guide_support_index.md.html#Platform%20Support The links to plugin docs are broken. e.g. http://cordova.apache.org/docs/en/3.4.0/cordova_accelerometer_accelerometer.md.html Is there a summary in one place of which plugin versions have been tested with a Cordova version? e.g. org.apache.cordova.camera@0.2.8 was released last week but accelerometer in a previous release. Would the platform support page be a good place to add this information? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6204) cordova run windows8 - fails - add test
[ https://issues.apache.org/jira/browse/CB-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925342#comment-13925342 ] Jesse MacFadyen commented on CB-6204: - Cool. Will eval tomorrow. > cordova run windows8 - fails - add test > --- > > Key: CB-6204 > URL: https://issues.apache.org/jira/browse/CB-6204 > Project: Apache Cordova > Issue Type: Bug > Components: Windows 8, WP8 >Affects Versions: Master > Environment: Windows 8.1 >Reporter: Jonathan Bond >Assignee: Jesse MacFadyen > Fix For: 3.5.0 > > > Running '.\tests\testRunProject', the application installs but fails to run. > I added a 'lib\common.js' which would make it easier to re-use code. Some > context, first noticed that 'msbuild' wasn't in my path so I was looking for > a fix. > I noticed windows8 is almost fixed but not wp8 (ideally could both share the > 'common.js' code). > - > Installing package... > Found dependency package(s): > F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\AppPackages\CordovaApp_1.0.0.0_AnyCPU_Debug_Test\Dependencies\Microsoft.WinJS.1.0.appx > Success: Your package was successfully installed. > powershell ". .\\cordova\lib\WindowsStoreAppUtils.ps1; Start-Locally > Cordova.Example > ActivateApplication: ! > Get-AppxPackageManifest : Cannot validate argument on parameter 'Package'. > The argument is null or empty. Provide an argument that is not null or empty, > and > then try the command again. > At > F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\cordova\lib\WindowsStoreAppUtils.ps1:108 > char:41 > + $manifest = Get-appxpackagemanifest $package > + > + CategoryInfo : InvalidData: (:) [Get-AppxPackageManifest], > ParameterBindingValidationException > + FullyQualifiedErrorId : > ParameterArgumentValidationError,Microsoft.Windows.Appx.PackageManager.Commands.GetAppxPackageManifestCommand > Exception calling "ActivateApplication" with "4" argument(s): "Value does not > fall within the expected range." > At > F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\cordova\lib\WindowsStoreAppUtils.ps1:115 > char:5 > + > $appActivator.ActivateApplication($applicationUserModelId,$null,[StoreAppRun > ... > + > > + CategoryInfo : NotSpecified: (:) [], MethodInvocationException > + FullyQualifiedErrorId : ArgumentException > powershell ". .\\cordova\lib\WindowsStoreAppUtils.ps1; Start-Locally > Cordova.Example -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CB-6175) Cannot add inAppBrowser plugin for android platform
[ https://issues.apache.org/jira/browse/CB-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Novak closed CB-6175. It is resolved in 0.3.3 version of inappbrowser. Thanks! > Cannot add inAppBrowser plugin for android platform > --- > > Key: CB-6175 > URL: https://issues.apache.org/jira/browse/CB-6175 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.4.0 > Environment: Xubuntu 13.10 64bit >Reporter: Michal Novak > Labels: cordova, inappbrowser > > Steps to reproduce: > cordova -v > 3.4.0-0.1.3 > cordova create test > cd test > cordova platform add android > cordova plugin add org.apache.cordova.inappbrowser > Error: ENOENT, no such file or directory > '/xxx/test/plugins/org.apache.cordova.inappbrowser/www/inappbrowser.js' > at Object.fs.openSync (fs.js:427:18) > at Object.fs.readFileSync (fs.js:284:15) > at /.../node_modules/cordova/node_modules/plugman/src/prepare.js:182:36 > at Array.forEach (native) > at /.../node_modules/cordova/node_modules/plugman/src/prepare.js:162:19 > at Array.forEach (native) > at Object.handlePrepare > (/.../node_modules/cordova/node_modules/plugman/src/prepare.js:128:24) > at /.../node_modules/cordova/node_modules/plugman/src/install.js:420:33 > at _fulfilled (/.../node_modules/cordova/node_modules/q/q.js:798:54) > at self.promiseDispatch.done > (/.../node_modules/cordova/node_modules/q/q.js:827:30) > (replaced cordova installation directory with /.../, project directory with > /xxx/) > I have installed cordova locally with npm (into /.../ directory) > npm install cordova@3.4.0-0.1.3 > and set PATH to /.../node_modules/cordova/bin > same is reproducible with 3.4.0-rc2 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6204) cordova run windows8 - fails - add test
[ https://issues.apache.org/jira/browse/CB-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925289#comment-13925289 ] Jonathan Bond commented on CB-6204: --- Pull request here: https://github.com/apache/cordova-windows/pull/19 It doesn't fix the bug though :/ > cordova run windows8 - fails - add test > --- > > Key: CB-6204 > URL: https://issues.apache.org/jira/browse/CB-6204 > Project: Apache Cordova > Issue Type: Bug > Components: Windows 8, WP8 >Affects Versions: Master > Environment: Windows 8.1 >Reporter: Jonathan Bond >Assignee: Jesse MacFadyen > Fix For: 3.5.0 > > > Running '.\tests\testRunProject', the application installs but fails to run. > I added a 'lib\common.js' which would make it easier to re-use code. Some > context, first noticed that 'msbuild' wasn't in my path so I was looking for > a fix. > I noticed windows8 is almost fixed but not wp8 (ideally could both share the > 'common.js' code). > - > Installing package... > Found dependency package(s): > F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\AppPackages\CordovaApp_1.0.0.0_AnyCPU_Debug_Test\Dependencies\Microsoft.WinJS.1.0.appx > Success: Your package was successfully installed. > powershell ". .\\cordova\lib\WindowsStoreAppUtils.ps1; Start-Locally > Cordova.Example > ActivateApplication: ! > Get-AppxPackageManifest : Cannot validate argument on parameter 'Package'. > The argument is null or empty. Provide an argument that is not null or empty, > and > then try the command again. > At > F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\cordova\lib\WindowsStoreAppUtils.ps1:108 > char:41 > + $manifest = Get-appxpackagemanifest $package > + > + CategoryInfo : InvalidData: (:) [Get-AppxPackageManifest], > ParameterBindingValidationException > + FullyQualifiedErrorId : > ParameterArgumentValidationError,Microsoft.Windows.Appx.PackageManager.Commands.GetAppxPackageManifestCommand > Exception calling "ActivateApplication" with "4" argument(s): "Value does not > fall within the expected range." > At > F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\cordova\lib\WindowsStoreAppUtils.ps1:115 > char:5 > + > $appActivator.ActivateApplication($applicationUserModelId,$null,[StoreAppRun > ... > + > > + CategoryInfo : NotSpecified: (:) [], MethodInvocationException > + FullyQualifiedErrorId : ArgumentException > powershell ". .\\cordova\lib\WindowsStoreAppUtils.ps1; Start-Locally > Cordova.Example -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6204) cordova run windows8 - fails - add test
Jonathan Bond created CB-6204: - Summary: cordova run windows8 - fails - add test Key: CB-6204 URL: https://issues.apache.org/jira/browse/CB-6204 Project: Apache Cordova Issue Type: Bug Components: Windows 8, WP8 Affects Versions: Master Environment: Windows 8.1 Reporter: Jonathan Bond Assignee: Jesse MacFadyen Fix For: 3.5.0 Running '.\tests\testRunProject', the application installs but fails to run. I added a 'lib\common.js' which would make it easier to re-use code. Some context, first noticed that 'msbuild' wasn't in my path so I was looking for a fix. I noticed windows8 is almost fixed but not wp8 (ideally could both share the 'common.js' code). - Installing package... Found dependency package(s): F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\AppPackages\CordovaApp_1.0.0.0_AnyCPU_Debug_Test\Dependencies\Microsoft.WinJS.1.0.appx Success: Your package was successfully installed. powershell ". .\\cordova\lib\WindowsStoreAppUtils.ps1; Start-Locally Cordova.Example ActivateApplication: ! Get-AppxPackageManifest : Cannot validate argument on parameter 'Package'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. At F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\cordova\lib\WindowsStoreAppUtils.ps1:108 char:41 + $manifest = Get-appxpackagemanifest $package + + CategoryInfo : InvalidData: (:) [Get-AppxPackageManifest], ParameterBindingValidationException + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Windows.Appx.PackageManager.Commands.GetAppxPackageManifestCommand Exception calling "ActivateApplication" with "4" argument(s): "Value does not fall within the expected range." At F:\Jonathan\GitHub\Cordova\gde\cordova-windows\windows8\tests\TestOutput\cordova\lib\WindowsStoreAppUtils.ps1:115 char:5 + $appActivator.ActivateApplication($applicationUserModelId,$null,[StoreAppRun ... + + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : ArgumentException powershell ". .\\cordova\lib\WindowsStoreAppUtils.ps1; Start-Locally Cordova.Example -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6203) CLI `npm test` failing on for plugins specs
Carlos Santana created CB-6203:
--
Summary: CLI `npm test` failing on for plugins specs
Key: CB-6203
URL: https://issues.apache.org/jira/browse/CB-6203
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: Master
Environment: osx 10.9
cordova@3.4.0-0.1.4-dev
$ node -v
v0.10.26
$ npm -v
1.4.3
Reporter: Carlos Santana
cd cordova-cli
npm test
or
cd cordova-cli
npm install ../cordova-plugman
npm test
same errors both ways
(master)$ npm test
> cordova@3.4.0-0.1.4-dev test /Users/csantana23/Documents/cordova/cordova-cli
> jasmine-node --color spec e2e
this is script 1 in
/private/var/folders/z3/nz0hg1s10r321pp8szx_2j08gn/T/e2e-test/hooks_test/project
this is script 0 in
/private/var/folders/z3/nz0hg1s10r321pp8szx_2j08gn/T/e2e-test/hooks_test/project
.F.F.
Failures:
1) plugin command success `add` should call plugman.fetch for each plugin
Message:
Expected spy fetch to have been called with [ 'one', 'some/path/plugins',
{ } ] but actual calls were [ 'one', 'some/path/plugins', { searchpath : [ ]
} ], [ 'two', 'some/path/plugins', { searchpath : [ ] } ]
Stacktrace:
Error: Expected spy fetch to have been called with [ 'one',
'some/path/plugins', { } ] but actual calls were [ 'one', 'some/path/plugins',
{ searchpath : [ ] } ], [ 'two', 'some/path/plugins', { searchpath : [ ] } ]
at new jasmine.ExpectationResult
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/jasmine-node/lib/jasmine-node/jasmine-1.3.1.js:114:32)
at null.toHaveBeenCalledWith
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/jasmine-node/lib/jasmine-node/jasmine-1.3.1.js:1235:29)
at
/Users/csantana23/Documents/cordova/cordova-cli/spec/plugin.spec.js:145:47
at Array.forEach (native)
at
/Users/csantana23/Documents/cordova/cordova-cli/spec/plugin.spec.js:144:36
at _fulfilled
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:798:54)
at self.promiseDispatch.done
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:827:30)
at Promise.promise.promiseDispatch
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:760:13)
at
/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:574:44
at flush
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:108:17)
2) plugin command success `add` should call plugman.fetch for each plugin
Message:
Expected spy fetch to have been called with [ 'two', 'some/path/plugins',
{ } ] but actual calls were [ 'one', 'some/path/plugins', { searchpath : [ ]
} ], [ 'two', 'some/path/plugins', { searchpath : [ ] } ]
Stacktrace:
Error: Expected spy fetch to have been called with [ 'two',
'some/path/plugins', { } ] but actual calls were [ 'one', 'some/path/plugins',
{ searchpath : [ ] } ], [ 'two', 'some/path/plugins', { searchpath : [ ] } ]
at new jasmine.ExpectationResult
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/jasmine-node/lib/jasmine-node/jasmine-1.3.1.js:114:32)
at null.toHaveBeenCalledWith
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/jasmine-node/lib/jasmine-node/jasmine-1.3.1.js:1235:29)
at
/Users/csantana23/Documents/cordova/cordova-cli/spec/plugin.spec.js:145:47
at Array.forEach (native)
at
/Users/csantana23/Documents/cordova/cordova-cli/spec/plugin.spec.js:144:36
at _fulfilled
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:798:54)
at self.promiseDispatch.done
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:827:30)
at Promise.promise.promiseDispatch
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:760:13)
at
/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:574:44
at flush
(/Users/csantana23/Documents/cordova/cordova-cli/node_modules/q/q.js:108:17)
3) plugin command success `add` should pass down variables into plugman
Message:
Expected spy install to have been called with [ 'amazon-fireos',
'some/path/platforms/amazon-fireos', 'one', 'some/path/plugins', {
cli_variables : { FOO : 'bar' } } ] but actual calls were [ 'amazon-fireos',
'some/path/platforms/amazon-fireos', 'one', 'some/path/plugins', {
cli_variables : { FOO : 'bar' }, searchpath : [ ] } ], [ 'android',
'some/path/platforms/android', 'one', 'some/path/plugins', { cli_variables : {
FOO : 'bar' }, searchpath : [ ] } ], [ 'blackberry10',
'some/path/platforms/blackberry10', 'one', 'some/path/plugins', { cli_variables
:
[jira] [Resolved] (CB-6157) Update wiki with instructions to refresh shrinkwrap.json for rc testing
[ https://issues.apache.org/jira/browse/CB-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Santana resolved CB-6157. Resolution: Fixed Fix Version/s: Master cordova-coho https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;a=commit;h=b68aa3c3b91173acf3afba2acf72f4c53a9e0bf6 > Update wiki with instructions to refresh shrinkwrap.json for rc testing > --- > > Key: CB-6157 > URL: https://issues.apache.org/jira/browse/CB-6157 > Project: Apache Cordova > Issue Type: Sub-task > Components: CLI, Plugman >Reporter: Carlos Santana >Assignee: Carlos Santana > Fix For: Master > > > I will also update the wiki [1] so its part of the process to refresh the > shrinkwrap.json before npm and npm publish for RC. > 1: http://wiki.apache.org/cordova/StepsForToolsRelease -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6147) Enable CLI and Plugman with npm shrinkwrap
[ https://issues.apache.org/jira/browse/CB-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Santana resolved CB-6147. Resolution: Fixed Fix Version/s: Master cordova-cli https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=commit;h=7df468b352b0681ea1b8558a723f2c4bd6afe191 cordova-plugman https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=7e26c88ab32532b4ef19b2950f654e9fa78fb3b8 cordova-coho https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;a=commit;h=b68aa3c3b91173acf3afba2acf72f4c53a9e0bf6 > Enable CLI and Plugman with npm shrinkwrap > -- > > Key: CB-6147 > URL: https://issues.apache.org/jira/browse/CB-6147 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI, Plugman >Affects Versions: Master >Reporter: Carlos Santana >Assignee: Carlos Santana > Fix For: Master > > > I think the npm modules cordova and plugman should be enable and publish with > shrinkwrap. > It doesn't mean that cordova-cli/plugman locks down dependency tree for ever, > they can be updated as needed at any time a new version if publish to npm. > More info here: > https://www.npmjs.org/doc/cli/npm-shrinkwrap.html > http://blog.nodejs.org/2012/02/27/managing-node-js-dependencies-with-shrinkwrap > This provides multiple benefits: > - Everyone testing cordova rc test the same code not just the cordova module, > but all its dependencies > - All users that npm install cordova or plugman get the same code including > all dependencies > - Easier to recreate an user environment, if user reports that is having > problems with cordova@3.4.0-0.1.0 then another cordova contributor or > committer wil be sure 100% that is running the same code as the user. > - Avoids "it works on my system and not yours" without shrinkwrap it depends > when an user installs cordova or plugman, and if any dependencies inside the > whole dependency tree changes a version > - Could be use to better clarify ALL dependencies including the versions that > cordova/plugman was tested, so if a downstream distribution or end user wants > to know what is a full list of dependencies to get cordova-cli and plugman > working they can take a look at shrinkwrap.json > - If a downstream distribution wants to redistribute cordova-cli and plugman, > then it has higher confident of what dependencies where use at time of > testing and releasing a specific version of cordov-cli/plugman, and if it > wants to distribute cordova-cli/plugman including its dependencies it's > easier to distribute only the versions that where use at time of > testing/release. > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6156) Generate shrinkwrap.json and update package.json to enable
[ https://issues.apache.org/jira/browse/CB-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925204#comment-13925204 ] ASF subversion and git services commented on CB-6156: - Commit b68aa3c3b91173acf3afba2acf72f4c53a9e0bf6 in cordova-coho's branch refs/heads/master from [~csantana] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=b68aa3c ] CB-6156 Enable CLI and Plugman with npm shrinkwrap > Generate shrinkwrap.json and update package.json to enable > -- > > Key: CB-6156 > URL: https://issues.apache.org/jira/browse/CB-6156 > Project: Apache Cordova > Issue Type: Sub-task > Components: CLI, Plugman >Reporter: Carlos Santana >Assignee: Carlos Santana > Fix For: Master > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6156) Generate shrinkwrap.json and update package.json to enable
[ https://issues.apache.org/jira/browse/CB-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Santana resolved CB-6156. Resolution: Fixed Fix Version/s: Master cordova-cli https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=commit;h=7df468b352b0681ea1b8558a723f2c4bd6afe191 cordova-plugman https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=7e26c88ab32532b4ef19b2950f654e9fa78fb3b8 > Generate shrinkwrap.json and update package.json to enable > -- > > Key: CB-6156 > URL: https://issues.apache.org/jira/browse/CB-6156 > Project: Apache Cordova > Issue Type: Sub-task > Components: CLI, Plugman >Reporter: Carlos Santana >Assignee: Carlos Santana > Fix For: Master > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6147) Enable CLI and Plugman with npm shrinkwrap
[ https://issues.apache.org/jira/browse/CB-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925199#comment-13925199 ] ASF subversion and git services commented on CB-6147: - Commit 7e26c88ab32532b4ef19b2950f654e9fa78fb3b8 in cordova-plugman's branch refs/heads/master from [~csantana] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=7e26c88 ] CB-6147 Enable CLI and Plugman with npm shrinkwrap > Enable CLI and Plugman with npm shrinkwrap > -- > > Key: CB-6147 > URL: https://issues.apache.org/jira/browse/CB-6147 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI, Plugman >Affects Versions: Master >Reporter: Carlos Santana >Assignee: Carlos Santana > > I think the npm modules cordova and plugman should be enable and publish with > shrinkwrap. > It doesn't mean that cordova-cli/plugman locks down dependency tree for ever, > they can be updated as needed at any time a new version if publish to npm. > More info here: > https://www.npmjs.org/doc/cli/npm-shrinkwrap.html > http://blog.nodejs.org/2012/02/27/managing-node-js-dependencies-with-shrinkwrap > This provides multiple benefits: > - Everyone testing cordova rc test the same code not just the cordova module, > but all its dependencies > - All users that npm install cordova or plugman get the same code including > all dependencies > - Easier to recreate an user environment, if user reports that is having > problems with cordova@3.4.0-0.1.0 then another cordova contributor or > committer wil be sure 100% that is running the same code as the user. > - Avoids "it works on my system and not yours" without shrinkwrap it depends > when an user installs cordova or plugman, and if any dependencies inside the > whole dependency tree changes a version > - Could be use to better clarify ALL dependencies including the versions that > cordova/plugman was tested, so if a downstream distribution or end user wants > to know what is a full list of dependencies to get cordova-cli and plugman > working they can take a look at shrinkwrap.json > - If a downstream distribution wants to redistribute cordova-cli and plugman, > then it has higher confident of what dependencies where use at time of > testing and releasing a specific version of cordov-cli/plugman, and if it > wants to distribute cordova-cli/plugman including its dependencies it's > easier to distribute only the versions that where use at time of > testing/release. > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6147) Enable CLI and Plugman with npm shrinkwrap
[ https://issues.apache.org/jira/browse/CB-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925196#comment-13925196 ] ASF subversion and git services commented on CB-6147: - Commit 7df468b352b0681ea1b8558a723f2c4bd6afe191 in cordova-cli's branch refs/heads/master from [~csantana] [ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=7df468b ] CB-6147 Enable CLI and Plugman with npm shrinkwrap > Enable CLI and Plugman with npm shrinkwrap > -- > > Key: CB-6147 > URL: https://issues.apache.org/jira/browse/CB-6147 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI, Plugman >Affects Versions: Master >Reporter: Carlos Santana >Assignee: Carlos Santana > > I think the npm modules cordova and plugman should be enable and publish with > shrinkwrap. > It doesn't mean that cordova-cli/plugman locks down dependency tree for ever, > they can be updated as needed at any time a new version if publish to npm. > More info here: > https://www.npmjs.org/doc/cli/npm-shrinkwrap.html > http://blog.nodejs.org/2012/02/27/managing-node-js-dependencies-with-shrinkwrap > This provides multiple benefits: > - Everyone testing cordova rc test the same code not just the cordova module, > but all its dependencies > - All users that npm install cordova or plugman get the same code including > all dependencies > - Easier to recreate an user environment, if user reports that is having > problems with cordova@3.4.0-0.1.0 then another cordova contributor or > committer wil be sure 100% that is running the same code as the user. > - Avoids "it works on my system and not yours" without shrinkwrap it depends > when an user installs cordova or plugman, and if any dependencies inside the > whole dependency tree changes a version > - Could be use to better clarify ALL dependencies including the versions that > cordova/plugman was tested, so if a downstream distribution or end user wants > to know what is a full list of dependencies to get cordova-cli and plugman > working they can take a look at shrinkwrap.json > - If a downstream distribution wants to redistribute cordova-cli and plugman, > then it has higher confident of what dependencies where use at time of > testing and releasing a specific version of cordov-cli/plugman, and if it > wants to distribute cordova-cli/plugman including its dependencies it's > easier to distribute only the versions that where use at time of > testing/release. > -- This message was sent by Atlassian JIRA (v6.2#6252)
