[jira] [Commented] (CB-14266) Documentation search is not working

[Shazron Abdullah (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-14266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579241#comment-16579241
 ] 

Shazron Abdullah commented on CB-14266:
---

Tested it on a local doc build -- not sure if its supposed to work on a 
localhost context, but it doesn't work there either.

> Documentation search is not working
> ---
>
> Key: CB-14266
> URL: https://issues.apache.org/jira/browse/CB-14266
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-docs
>Reporter: Shazron Abdullah
>Priority: Major
>
> cordova.apache.org
> We are using Algolia search. It may be related to https changes we did. Need 
> to investigate.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Created] (CB-14266) Documentation search is not working

[Shazron Abdullah (JIRA)]

Shazron Abdullah created CB-14266:
-

 Summary: Documentation search is not working
 Key: CB-14266
 URL: https://issues.apache.org/jira/browse/CB-14266
 Project: Apache Cordova
  Issue Type: Bug
  Components: cordova-docs
Reporter: Shazron Abdullah


cordova.apache.org

We are using Algolia search. It may be related to https changes we did. Need to 
investigate.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Updated] (CB-14265) Plugin search is not working

[Shazron Abdullah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-14265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shazron Abdullah updated CB-14265:
--
Attachment: pluginsearch.png

> Plugin search is not working
> 
>
> Key: CB-14265
> URL: https://issues.apache.org/jira/browse/CB-14265
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-docs
>Reporter: Shazron Abdullah
>Priority: Major
> Attachments: pluginsearch.png
>
>
> The npmsearch API call we use used to return XML, now it returns json.
> See attached image.
> We really should move off to CB-12602



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Updated] (CB-14265) Plugin search is not working

[Shazron Abdullah (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-14265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shazron Abdullah updated CB-14265:
--
Description: 
The npmsearch API call we use used to return XML, now it returns json.
See attached image.

We really should move off to CB-12602

  was:
The npmsearch API call we use used to return XML, now it returns json.
See attached image.


> Plugin search is not working
> 
>
> Key: CB-14265
> URL: https://issues.apache.org/jira/browse/CB-14265
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-docs
>Reporter: Shazron Abdullah
>Priority: Major
>
> The npmsearch API call we use used to return XML, now it returns json.
> See attached image.
> We really should move off to CB-12602



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Created] (CB-14265) Plugin search is not working

[Shazron Abdullah (JIRA)]

Shazron Abdullah created CB-14265:
-

 Summary: Plugin search is not working
 Key: CB-14265
 URL: https://issues.apache.org/jira/browse/CB-14265
 Project: Apache Cordova
  Issue Type: Bug
  Components: cordova-docs
Reporter: Shazron Abdullah


The npmsearch API call we use used to return XML, now it returns json.
See attached image.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Commented] (CB-14228) cordova-osx patch release July 2018

[Chris Brody (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578295#comment-16578295
 ] 

Chris Brody commented on CB-14228:
--

I just opened  to track the 
issue with  () in patch 
release, would like to continue the discussion there.

> cordova-osx patch release July 2018
> ---
>
> Key: CB-14228
> URL: https://issues.apache.org/jira/browse/CB-14228
> Project: Apache Cordova
>  Issue Type: Task
>  Components: cordova-osx
>Reporter: Chris Brody
>Assignee: Chris Brody
>Priority: Major
>
> Patch release of cordova-osx package with CB-14145 (npm audit issues) 
> resolved.
> Following steps at 
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
>  (with some modifications)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Updated] (CB-14145) Resolve npm audit issues in platforms - patch updates

[Chris Brody (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-14145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Brody updated CB-14145:
-
Description: 
>From private discussions I discovered that running {{npm audit}} on a number 
>of components would report dependencies with security issues. While we could 
>not see any {{npm audit}} issues that may affect applications built using 
>Cordova I think it is extremely important to resolve these issues as soon as 
>possible. Most affect devDependencies used for testing of Cordova itself; a 
>minority seem to affect Cordova scripts that may be run by Cordova application 
>developers. Better safe than sorry!

I would like to resolve this issue as follows:
* patch release of common library components such as {{cordova-common}}, 
-{{cordova-lib}}, etc.- (fixed in minor release branch) _- solution for other 
components to be tracked on GitHub, moved out of the scope of this issue_
* patch or minor release of -other affected components such as CLI,- Cordova 
platform implementations, -major plugins, etc.- (expected to be fixed in minor 
release branch; do not want to pollute the master branch with extra reverts, 
updated node_modules committed, etc.) _- solution for other components to be 
tracked on GitHub, moved out of the scope of this issue_
* -{{npm audit}} issues resolved in master branch for next major release, which 
should NOT be shipped with any {{npm audit}} issues lurking- _- to be tracked 
on GitHub, as part of general update of dependencies, moved out of the scope of 
this issue_
* -{{npm audit}} step added to CI for both patch release and next major 
release- _(not wanted)_

  was:
>From private discussions I discovered that running {{npm audit}} on a number 
>of components would report dependencies with security issues. While we could 
>not see any {{npm audit}} issues that may affect applications built using 
>Cordova I think it is extremely important to resolve these issues as soon as 
>possible. Most affect devDependencies used for testing of Cordova itself; a 
>minority seem to affect Cordova scripts that may be run by Cordova application 
>developers. Better safe than sorry!

I would like to resolve this issue as follows:
* patch release of common library components such as {{cordova-common}}, 
{{cordova-lib}}, etc. (fixed in minor release branch)
* patch or minor release of other affected components such as CLI, Cordova 
platform implementations, major plugins, etc. (expected to be fixed in minor 
release branch; do not want to pollute the master branch with extra reverts, 
updated node_modules committed, etc.)
* {{npm audit}} issues resolved in master branch for next major release, which 
should NOT be shipped with any {{npm audit}} issues lurking
* {{npm audit}} step added to CI for both patch release and next major release


> Resolve npm audit issues in platforms - patch updates
> -
>
> Key: CB-14145
> URL: https://issues.apache.org/jira/browse/CB-14145
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-android, cordova-browser, cordova-coho, 
> cordova-common, cordova-ios, cordova-js, cordova-osx, cordova-windows
>Reporter: Chris Brody
>Assignee: Chris Brody
>Priority: Major
>
> From private discussions I discovered that running {{npm audit}} on a number 
> of components would report dependencies with security issues. While we could 
> not see any {{npm audit}} issues that may affect applications built using 
> Cordova I think it is extremely important to resolve these issues as soon as 
> possible. Most affect devDependencies used for testing of Cordova itself; a 
> minority seem to affect Cordova scripts that may be run by Cordova 
> application developers. Better safe than sorry!
> I would like to resolve this issue as follows:
> * patch release of common library components such as {{cordova-common}}, 
> -{{cordova-lib}}, etc.- (fixed in minor release branch) _- solution for other 
> components to be tracked on GitHub, moved out of the scope of this issue_
> * patch or minor release of -other affected components such as CLI,- Cordova 
> platform implementations, -major plugins, etc.- (expected to be fixed in 
> minor release branch; do not want to pollute the master branch with extra 
> reverts, updated node_modules committed, etc.) _- solution for other 
> components to be tracked on GitHub, moved out of the scope of this issue_
> * -{{npm audit}} issues resolved in master branch for next major release, 
> which should NOT be shipped with any {{npm audit}} issues lurking- _- to be 
> tracked on GitHub, as part of general update of dependencies, moved out of 
> the scope of this issue_
> * -{{npm audit}} step added to CI for both patch release and next major 
> release- _(not wanted)_



--
This message was sent by Atlassi

[jira] [Resolved] (CB-14145) Resolve npm audit issues in platforms - patch updates

[Chris Brody (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-14145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Brody resolved CB-14145.
--
Resolution: Fixed

> Resolve npm audit issues in platforms - patch updates
> -
>
> Key: CB-14145
> URL: https://issues.apache.org/jira/browse/CB-14145
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-android, cordova-browser, cordova-coho, 
> cordova-common, cordova-ios, cordova-js, cordova-osx, cordova-windows
>Reporter: Chris Brody
>Assignee: Chris Brody
>Priority: Major
>
> From private discussions I discovered that running {{npm audit}} on a number 
> of components would report dependencies with security issues. While we could 
> not see any {{npm audit}} issues that may affect applications built using 
> Cordova I think it is extremely important to resolve these issues as soon as 
> possible. Most affect devDependencies used for testing of Cordova itself; a 
> minority seem to affect Cordova scripts that may be run by Cordova 
> application developers. Better safe than sorry!
> I would like to resolve this issue as follows:
> * patch release of common library components such as {{cordova-common}}, 
> -{{cordova-lib}}, etc.- (fixed in minor release branch) _- solution for other 
> components to be tracked on GitHub, moved out of the scope of this issue_
> * patch or minor release of -other affected components such as CLI,- Cordova 
> platform implementations, -major plugins, etc.- (expected to be fixed in 
> minor release branch; do not want to pollute the master branch with extra 
> reverts, updated node_modules committed, etc.) _- solution for other 
> components to be tracked on GitHub, moved out of the scope of this issue_
> * -{{npm audit}} issues resolved in master branch for next major release, 
> which should NOT be shipped with any {{npm audit}} issues lurking- _- to be 
> tracked on GitHub, as part of general update of dependencies, moved out of 
> the scope of this issue_
> * -{{npm audit}} step added to CI for both patch release and next major 
> release- _(not wanted)_



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Commented] (CB-14145) Resolve npm audit issues in platforms - patch updates

[Chris Brody (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-14145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578234#comment-16578234
 ] 

Chris Brody commented on CB-14145:
--

Limiting the scope of this issue to {{cordova-coho}}, {{cordova-common}}, and 
Cordova platforms in patch release which has already been done. Resolving {{npm 
audit}} issues in other components will be tracked on GitHub. Resolving {{npm 
audit}} issues on {{master}} for next major release will be tracked on GitHub 
and should be part of general dependency updates.

> Resolve npm audit issues in platforms - patch updates
> -
>
> Key: CB-14145
> URL: https://issues.apache.org/jira/browse/CB-14145
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-android, cordova-browser, cordova-coho, 
> cordova-common, cordova-ios, cordova-js, cordova-osx, cordova-windows
>Reporter: Chris Brody
>Assignee: Chris Brody
>Priority: Major
>
> From private discussions I discovered that running {{npm audit}} on a number 
> of components would report dependencies with security issues. While we could 
> not see any {{npm audit}} issues that may affect applications built using 
> Cordova I think it is extremely important to resolve these issues as soon as 
> possible. Most affect devDependencies used for testing of Cordova itself; a 
> minority seem to affect Cordova scripts that may be run by Cordova 
> application developers. Better safe than sorry!
> I would like to resolve this issue as follows:
> * patch release of common library components such as {{cordova-common}}, 
> {{cordova-lib}}, etc. (fixed in minor release branch)
> * patch or minor release of other affected components such as CLI, Cordova 
> platform implementations, major plugins, etc. (expected to be fixed in minor 
> release branch; do not want to pollute the master branch with extra reverts, 
> updated node_modules committed, etc.)
> * {{npm audit}} issues resolved in master branch for next major release, 
> which should NOT be shipped with any {{npm audit}} issues lurking
> * {{npm audit}} step added to CI for both patch release and next major release



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Updated] (CB-14145) Resolve npm audit issues in platforms - patch updates

[Chris Brody (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-14145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Brody updated CB-14145:
-
Summary: Resolve npm audit issues in platforms - patch updates  (was: 
Resolve npm audit issues)

> Resolve npm audit issues in platforms - patch updates
> -
>
> Key: CB-14145
> URL: https://issues.apache.org/jira/browse/CB-14145
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-android, cordova-browser, cordova-coho, 
> cordova-common, cordova-ios, cordova-js, cordova-osx, cordova-windows
>Reporter: Chris Brody
>Assignee: Chris Brody
>Priority: Major
>
> From private discussions I discovered that running {{npm audit}} on a number 
> of components would report dependencies with security issues. While we could 
> not see any {{npm audit}} issues that may affect applications built using 
> Cordova I think it is extremely important to resolve these issues as soon as 
> possible. Most affect devDependencies used for testing of Cordova itself; a 
> minority seem to affect Cordova scripts that may be run by Cordova 
> application developers. Better safe than sorry!
> I would like to resolve this issue as follows:
> * patch release of common library components such as {{cordova-common}}, 
> {{cordova-lib}}, etc. (fixed in minor release branch)
> * patch or minor release of other affected components such as CLI, Cordova 
> platform implementations, major plugins, etc. (expected to be fixed in minor 
> release branch; do not want to pollute the master branch with extra reverts, 
> updated node_modules committed, etc.)
> * {{npm audit}} issues resolved in master branch for next major release, 
> which should NOT be shipped with any {{npm audit}} issues lurking
> * {{npm audit}} step added to CI for both patch release and next major release



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Updated] (CB-14145) Resolve npm audit issues

[Chris Brody (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-14145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Brody updated CB-14145:
-
Component/s: (was: cordova-plugman)
 (was: cordova-lib)
 (was: cordova-cli)
 (was: cordova-app-hello-world)

> Resolve npm audit issues
> 
>
> Key: CB-14145
> URL: https://issues.apache.org/jira/browse/CB-14145
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-android, cordova-browser, cordova-coho, 
> cordova-common, cordova-ios, cordova-js, cordova-osx, cordova-windows
>Reporter: Chris Brody
>Assignee: Chris Brody
>Priority: Major
>
> From private discussions I discovered that running {{npm audit}} on a number 
> of components would report dependencies with security issues. While we could 
> not see any {{npm audit}} issues that may affect applications built using 
> Cordova I think it is extremely important to resolve these issues as soon as 
> possible. Most affect devDependencies used for testing of Cordova itself; a 
> minority seem to affect Cordova scripts that may be run by Cordova 
> application developers. Better safe than sorry!
> I would like to resolve this issue as follows:
> * patch release of common library components such as {{cordova-common}}, 
> {{cordova-lib}}, etc. (fixed in minor release branch)
> * patch or minor release of other affected components such as CLI, Cordova 
> platform implementations, major plugins, etc. (expected to be fixed in minor 
> release branch; do not want to pollute the master branch with extra reverts, 
> updated node_modules committed, etc.)
> * {{npm audit}} issues resolved in master branch for next major release, 
> which should NOT be shipped with any {{npm audit}} issues lurking
> * {{npm audit}} step added to CI for both patch release and next major release



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Comment Edited] (CB-14228) cordova-osx patch release July 2018

[Bryan Ellis (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578014#comment-16578014
 ] 

Bryan Ellis edited comment on CB-14228 at 8/13/18 9:34 AM:
---

[~brodybits] I am not sure where to bring up this issue. I noticed the VOTE 
thread and the thread had nothing about where to bring up a discussion 
point/concern.

In the vote, I noticed that the `cordova-common` dep is still on 2.x. 

In `cordova-common` 2.x there was a bug reported which I committed a PR and fix 
for, but, it is only in 3.0.0-dev. Should this fix be cherry-picked and release 
in 2.x of common and then bump OSX platform to that version?

*The gist of the issue*
When you add a plugin and build the first time, it will trigger the device 
ready. This is expected. But if you build a second or third or any thereafter, 
the device is ready is not triggered.

https://issues.apache.org/jira/browse/CB-14099
https://github.com/apache/cordova-common/pull/32

Please note, even though the PR says closed, the fix was merged into master... 
It seems the person used coho to merge my changes and it closed my PR instead.


was (Author: erisu):
[~brodybits] I am not sure where to bring up this issue. I noticed the VOTE 
thread and the thread had nothing about where to discuss.

In the vote, I noticed that the `cordova-common` dep is still on 2.x. 

In `cordova-common` 2.x there was a bug reported which I committed a PR and fix 
for, but, it is only in 3.0.0-dev. Should this fix be cherry-picked and release 
in 2.x of common and then bump OSX platform to that version?

*The gist of the issue*
When you add a plugin and build the first time, it will trigger the device 
ready. This is expected. But if you build a second or third or any thereafter, 
the device is ready is not triggered.

https://issues.apache.org/jira/browse/CB-14099
https://github.com/apache/cordova-common/pull/32

Please note, even though the PR says closed, the fix was merged into master... 
It seems the person used coho to merge my changes and it closed my PR instead.

> cordova-osx patch release July 2018
> ---
>
> Key: CB-14228
> URL: https://issues.apache.org/jira/browse/CB-14228
> Project: Apache Cordova
>  Issue Type: Task
>  Components: cordova-osx
>Reporter: Chris Brody
>Assignee: Chris Brody
>Priority: Major
>
> Patch release of cordova-osx package with CB-14145 (npm audit issues) 
> resolved.
> Following steps at 
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
>  (with some modifications)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Commented] (CB-14228) cordova-osx patch release July 2018

[Bryan Ellis (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578014#comment-16578014
 ] 

Bryan Ellis commented on CB-14228:
--

[~brodybits] I am not sure where to bring up this issue. I noticed the VOTE 
thread and the thread had nothing about where to discuss.

In the vote, I noticed that the `cordova-common` dep is still on 2.x. 

In `cordova-common` 2.x there was a bug reported which I committed a PR and fix 
for, but, it is only in 3.0.0-dev. Should this fix be cherry-picked and release 
in 2.x of common and then bump OSX platform to that version?

*The gist of the issue*
When you add a plugin and build the first time, it will trigger the device 
ready. This is expected. But if you build a second or third or any thereafter, 
the device is ready is not triggered.

https://issues.apache.org/jira/browse/CB-14099
https://github.com/apache/cordova-common/pull/32

Please note, even though the PR says closed, the fix was merged into master... 
It seems the person used coho to merge my changes and it closed my PR instead.

> cordova-osx patch release July 2018
> ---
>
> Key: CB-14228
> URL: https://issues.apache.org/jira/browse/CB-14228
> Project: Apache Cordova
>  Issue Type: Task
>  Components: cordova-osx
>Reporter: Chris Brody
>Assignee: Chris Brody
>Priority: Major
>
> Patch release of cordova-osx package with CB-14145 (npm audit issues) 
> resolved.
> Following steps at 
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
>  (with some modifications)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

[jira] [Commented] (CB-14165) Android Emulator gives 'device still connecting' error regardless of API version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-14165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577978#comment-16577978
 ] 

ASF GitHub Bot commented on CB-14165:
-

MatanYed commented on issue #457: CB-14165 : (android) Fix for device still 
connecting issues
URL: https://github.com/apache/cordova-android/pull/457#issuecomment-412451703
 
 
   +1 guys just release the fix


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Android Emulator gives 'device still connecting' error regardless of API 
> version
> 
>
> Key: CB-14165
> URL: https://issues.apache.org/jira/browse/CB-14165
> Project: Apache Cordova
>  Issue Type: Bug
>Reporter: Rizal Solichudin
>Priority: Minor
>
> cordova emulate android gives error
> (node:4822) UnhandledPromiseRejectionWarning: Unhandled promise rejection 
> (rejection id: 1): Failed to execute shell command 
> "getprop,dev.bootcomplete"" on device: Error: adb: Command failed with exit 
> code 1 Error output: error: device still connecting
> even though the device is launched successfully



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org