subject:"Facing issue in testing release process of Cordova platforms"

Re: Facing issue in testing release process of Cordova platforms

2018-11-02 Thread gandhi rajan

Hi Jan,

Thanks for the response again. Please find my response inline.

On Thu, Nov 1, 2018 at 10:46 PM Jan Piotrowski  wrote:

> The documented command actually is just
> "./cordova-mobile-spec/createmobilespec/createmobilespec.js --android
> --forceplugins", without the "node" in front of it. But I am not sure
> if this is correct or just a bug in the documentation.
>
   *The documented command does not include node but this needs to be
included in order to run the js file in windows OS. As I mentioned earlier,*
*the existing documentation is more macOS oriented.*

>
> Please reply with the full command you are executing and the full
> output you are getting.
>

 *Please find the complete error trace on executing the documented command
and command with node in the link - https://imgur.com/a/tLyEWkq
 *


>
> > I did install cordova-js and cordova-lib modules ...
>
> Where did you run which command exactly to try to fix this?
>

  *I navigated to the respective folders and executed 'npm install'
command *

>
> Best,
> Jan
>
> PS: Yep, mobilespec is heavily underdocumented as most of the testing
> stuff.
>
>
> Am Do., 1. Nov. 2018 um 18:10 Uhr schrieb gandhi rajan
> :
> >
> > Hi Jan,
> >
> > Thanks for your response. I did checkout  all repos using the coho
> command
> > - "coho repo-update -g -r all"
> >
> > While trying to do plugin tests as mentioned in
> >
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#1-plugin-tests-with-cordova-mobile-spec-project
> ,
> > I executed the following command in my windows system:
> >
> > "node ./cordova-mobile-spec/createmobilespec/createmobilespec.js
> --android
> > --forceplugins"
> >
> > I got the following error while executing the above command:
> >
> > "Error: Module cordova-js is not installed at all (direct or npm-linked)
> in
> > cordova-lib"
> >
> > I did install cordova-js and cordova-lib modules but couldn't get away
> from
> > this error. Jesse did pointed out that we dont do this test until we make
> > some breaking changes in platform but just curious to resolve this issue
> as
> > we may encounter this error anytime in future.
> >
> > Let me know your thoughts.
> >
> > On Wed, Oct 31, 2018 at 11:07 PM Jan Piotrowski 
> > wrote:
> >
> > > Gandhi, what exactly did you do until now? Do you have a checkout of
> > > all the Cordova repos created with coho?
> > >
> > > Please reply with the exact command you are running and error/output
> > > you are getting.
> > >
> > > J
> > > Am Sa., 27. Okt. 2018 um 11:02 Uhr schrieb gandhi rajan
> > > :
> > > >
> > > > Hi Raphinesse, Thanks for the Jasmine 3 update. I m now able to
> build and
> > > > install cordova-js module.
> > > >
> > > > @jesse, I tried the steps you mentioned to test platform and it
> works.
> > > But
> > > > I m still not able to create and run mobile-spec project.While
> running
> > > the
> > > > following command - "node
> > > > cordova-mobile-spec\createmobilespec\createmobilespec.js --android
> > > > --forceplugins", I get the following error - Error: Module
> cordova-js is
> > > > not installed at all (direct or npm-linked) in cordova-lib
> > > >
> > > > Any thoughts on this?
> > > >
> > > > On Thu, Oct 25, 2018 at 11:43 PM gandhi rajan <
> gandhiraja...@gmail.com>
> > > > wrote:
> > > >
> > > > > Thanks a lot for the response Jesse and Raphinesse. Will try out
> the
> > > > > suggested steps and check out the merge as well. Will get back with
> > > further
> > > > > updates if I m stuck.
> > > > >
> > > > > On Thursday, October 25, 2018,  wrote:
> > > > >
> > > > >> I already updated cordova-js to use more modern tooling some time
> ago
> > > in
> > > > >> https://github.com/apache/cordova-js/pull/176.  I just had not
> gotten
> > > > >> around to merging it yet. I did so just now.
> > > > >>
> > > > >> Jesse  schrieb am Do., 25. Okt. 2018,
> 10:19:
> > > > >>
> > > > >> > Hi Gandhi,
> > > > >> >
> > > > >> > There is an issue with this repo in that cordova-js uses a
> > > jasmine-node
> > > > >> > version that depends on a non-secure version of growl.  This is
> not
> > > a
> > > > >> > trivial fix as moving to the recommended jasmine-node@2.0.1 is
> a
> > > > >> breaking
> > > > >> > change.
> > > > >> > I am not completely of the mind that updating is the right
> approach
> > > > >> here,
> > > > >> > as I think in many ways the cordova-js project is outdated, and
> the
> > > > >> whole
> > > > >> > process of generating platform specific cordova.js files needs
> to be
> > > > >> > rethought.
> > > > >> >
> > > > >> > Personally, this does not block me ... I do the following:
> > > > >> > ⚡ npm i
> > > > >> > audited 684 packages in 2.085s
> > > > >> > found 1 critical severity vulnerability
> > > > >> >   run `npm audit fix` to fix them, or `npm audit` for details
> > > > >> >
> > > > >> > ⚡ npx grunt
> > > > >> > ... succeeds
> > > > >> >
> > > > >> > ⚡ npx grunt compile:windows
> > > > >> > Running "compile:windows

Re: Facing issue in testing release process of Cordova platforms

2018-11-01 Thread Jan Piotrowski

The documented command actually is just
"./cordova-mobile-spec/createmobilespec/createmobilespec.js --android
--forceplugins", without the "node" in front of it. But I am not sure
if this is correct or just a bug in the documentation.

Please reply with the full command you are executing and the full
output you are getting.

> I did install cordova-js and cordova-lib modules ...

Where did you run which command exactly to try to fix this?

Best,
Jan

PS: Yep, mobilespec is heavily underdocumented as most of the testing stuff.


Am Do., 1. Nov. 2018 um 18:10 Uhr schrieb gandhi rajan
:
>
> Hi Jan,
>
> Thanks for your response. I did checkout  all repos using the coho command
> - "coho repo-update -g -r all"
>
> While trying to do plugin tests as mentioned in
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#1-plugin-tests-with-cordova-mobile-spec-project,
> I executed the following command in my windows system:
>
> "node ./cordova-mobile-spec/createmobilespec/createmobilespec.js --android
> --forceplugins"
>
> I got the following error while executing the above command:
>
> "Error: Module cordova-js is not installed at all (direct or npm-linked) in
> cordova-lib"
>
> I did install cordova-js and cordova-lib modules but couldn't get away from
> this error. Jesse did pointed out that we dont do this test until we make
> some breaking changes in platform but just curious to resolve this issue as
> we may encounter this error anytime in future.
>
> Let me know your thoughts.
>
> On Wed, Oct 31, 2018 at 11:07 PM Jan Piotrowski 
> wrote:
>
> > Gandhi, what exactly did you do until now? Do you have a checkout of
> > all the Cordova repos created with coho?
> >
> > Please reply with the exact command you are running and error/output
> > you are getting.
> >
> > J
> > Am Sa., 27. Okt. 2018 um 11:02 Uhr schrieb gandhi rajan
> > :
> > >
> > > Hi Raphinesse, Thanks for the Jasmine 3 update. I m now able to build and
> > > install cordova-js module.
> > >
> > > @jesse, I tried the steps you mentioned to test platform and it works.
> > But
> > > I m still not able to create and run mobile-spec project.While running
> > the
> > > following command - "node
> > > cordova-mobile-spec\createmobilespec\createmobilespec.js --android
> > > --forceplugins", I get the following error - Error: Module cordova-js is
> > > not installed at all (direct or npm-linked) in cordova-lib
> > >
> > > Any thoughts on this?
> > >
> > > On Thu, Oct 25, 2018 at 11:43 PM gandhi rajan 
> > > wrote:
> > >
> > > > Thanks a lot for the response Jesse and Raphinesse. Will try out the
> > > > suggested steps and check out the merge as well. Will get back with
> > further
> > > > updates if I m stuck.
> > > >
> > > > On Thursday, October 25, 2018,  wrote:
> > > >
> > > >> I already updated cordova-js to use more modern tooling some time ago
> > in
> > > >> https://github.com/apache/cordova-js/pull/176.  I just had not gotten
> > > >> around to merging it yet. I did so just now.
> > > >>
> > > >> Jesse  schrieb am Do., 25. Okt. 2018, 10:19:
> > > >>
> > > >> > Hi Gandhi,
> > > >> >
> > > >> > There is an issue with this repo in that cordova-js uses a
> > jasmine-node
> > > >> > version that depends on a non-secure version of growl.  This is not
> > a
> > > >> > trivial fix as moving to the recommended jasmine-node@2.0.1 is a
> > > >> breaking
> > > >> > change.
> > > >> > I am not completely of the mind that updating is the right approach
> > > >> here,
> > > >> > as I think in many ways the cordova-js project is outdated, and the
> > > >> whole
> > > >> > process of generating platform specific cordova.js files needs to be
> > > >> > rethought.
> > > >> >
> > > >> > Personally, this does not block me ... I do the following:
> > > >> > ⚡ npm i
> > > >> > audited 684 packages in 2.085s
> > > >> > found 1 critical severity vulnerability
> > > >> >   run `npm audit fix` to fix them, or `npm audit` for details
> > > >> >
> > > >> > ⚡ npx grunt
> > > >> > ... succeeds
> > > >> >
> > > >> > ⚡ npx grunt compile:windows
> > > >> > Running "compile:windows" (compile) task
> > > >> > generated cordova.windows.js @
> > 243e7aac8cee0108927df0253118e36857ab9fc7
> > > >> in
> > > >> > 5ms
> > > >> > Done.
> > > >> >
> > > >> > The typical way a platform is released is to use cordova-coho.
> > > >> > ex. `coho prepare-platform-release-branch -r cordova-android
> > --version
> > > >> > 9.9.9`
> > > >> > This takes care of all the tagging, building/copying of cordova.js
> > to
> > > >> the
> > > >> > correct platform folder.
> > > >> >
> > > >> > About the mobile-spec workflow, I have not done this is a long time,
> > > >> this
> > > >> > was more important when we were breaking things a lot.  One
> > expectation
> > > >> of
> > > >> > the tooling that may not be explicitly listed is that all repos are
> > > >> > expected to be cloned as peers.  cordova-coho has commands that can
> > help
> > > >> > manage the multitude of repos for you

Re: Facing issue in testing release process of Cordova platforms

2018-11-01 Thread gandhi rajan

Hi Jan,

Thanks for your response. I did checkout  all repos using the coho command
- "coho repo-update -g -r all"

While trying to do plugin tests as mentioned in
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#1-plugin-tests-with-cordova-mobile-spec-project,
I executed the following command in my windows system:

"node ./cordova-mobile-spec/createmobilespec/createmobilespec.js --android
--forceplugins"

I got the following error while executing the above command:

"Error: Module cordova-js is not installed at all (direct or npm-linked) in
cordova-lib"

I did install cordova-js and cordova-lib modules but couldn't get away from
this error. Jesse did pointed out that we dont do this test until we make
some breaking changes in platform but just curious to resolve this issue as
we may encounter this error anytime in future.

Let me know your thoughts.

On Wed, Oct 31, 2018 at 11:07 PM Jan Piotrowski 
wrote:

> Gandhi, what exactly did you do until now? Do you have a checkout of
> all the Cordova repos created with coho?
>
> Please reply with the exact command you are running and error/output
> you are getting.
>
> J
> Am Sa., 27. Okt. 2018 um 11:02 Uhr schrieb gandhi rajan
> :
> >
> > Hi Raphinesse, Thanks for the Jasmine 3 update. I m now able to build and
> > install cordova-js module.
> >
> > @jesse, I tried the steps you mentioned to test platform and it works.
> But
> > I m still not able to create and run mobile-spec project.While running
> the
> > following command - "node
> > cordova-mobile-spec\createmobilespec\createmobilespec.js --android
> > --forceplugins", I get the following error - Error: Module cordova-js is
> > not installed at all (direct or npm-linked) in cordova-lib
> >
> > Any thoughts on this?
> >
> > On Thu, Oct 25, 2018 at 11:43 PM gandhi rajan 
> > wrote:
> >
> > > Thanks a lot for the response Jesse and Raphinesse. Will try out the
> > > suggested steps and check out the merge as well. Will get back with
> further
> > > updates if I m stuck.
> > >
> > > On Thursday, October 25, 2018,  wrote:
> > >
> > >> I already updated cordova-js to use more modern tooling some time ago
> in
> > >> https://github.com/apache/cordova-js/pull/176.  I just had not gotten
> > >> around to merging it yet. I did so just now.
> > >>
> > >> Jesse  schrieb am Do., 25. Okt. 2018, 10:19:
> > >>
> > >> > Hi Gandhi,
> > >> >
> > >> > There is an issue with this repo in that cordova-js uses a
> jasmine-node
> > >> > version that depends on a non-secure version of growl.  This is not
> a
> > >> > trivial fix as moving to the recommended jasmine-node@2.0.1 is a
> > >> breaking
> > >> > change.
> > >> > I am not completely of the mind that updating is the right approach
> > >> here,
> > >> > as I think in many ways the cordova-js project is outdated, and the
> > >> whole
> > >> > process of generating platform specific cordova.js files needs to be
> > >> > rethought.
> > >> >
> > >> > Personally, this does not block me ... I do the following:
> > >> > ⚡ npm i
> > >> > audited 684 packages in 2.085s
> > >> > found 1 critical severity vulnerability
> > >> >   run `npm audit fix` to fix them, or `npm audit` for details
> > >> >
> > >> > ⚡ npx grunt
> > >> > ... succeeds
> > >> >
> > >> > ⚡ npx grunt compile:windows
> > >> > Running "compile:windows" (compile) task
> > >> > generated cordova.windows.js @
> 243e7aac8cee0108927df0253118e36857ab9fc7
> > >> in
> > >> > 5ms
> > >> > Done.
> > >> >
> > >> > The typical way a platform is released is to use cordova-coho.
> > >> > ex. `coho prepare-platform-release-branch -r cordova-android
> --version
> > >> > 9.9.9`
> > >> > This takes care of all the tagging, building/copying of cordova.js
> to
> > >> the
> > >> > correct platform folder.
> > >> >
> > >> > About the mobile-spec workflow, I have not done this is a long time,
> > >> this
> > >> > was more important when we were breaking things a lot.  One
> expectation
> > >> of
> > >> > the tooling that may not be explicitly listed is that all repos are
> > >> > expected to be cloned as peers.  cordova-coho has commands that can
> help
> > >> > manage the multitude of repos for you.
> > >> >
> > >> > Not sure if this helps you move forward, I am happy to dig into this
> > >> more
> > >> > with you.
> > >> >
> > >> > Cheers,
> > >> >   Jesse
> > >> >
> > >> > @purplecabbage
> > >> > risingj.com
> > >> >
> > >> >
> > >> > On Tue, Oct 23, 2018 at 10:22 PM gandhi rajan <
> gandhiraja...@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > Hi All,
> > >> > >
> > >> > > I was trying to understand the release process for Cordova
> platforms
> > >> as
> > >> > > mentioned in the following link -
> > >> > >
> > >> > >
> > >> >
> > >>
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
> > >> > > .
> > >> > >
> > >> > > While following the steps mentioned to test plugins with
> > >> > > cordova-mobile-spec project, I got an error stating cordova-js
> module
> > >> is
>

Re: Facing issue in testing release process of Cordova platforms

2018-10-31 Thread Jan Piotrowski

Gandhi, what exactly did you do until now? Do you have a checkout of
all the Cordova repos created with coho?

Please reply with the exact command you are running and error/output
you are getting.

J
Am Sa., 27. Okt. 2018 um 11:02 Uhr schrieb gandhi rajan
:
>
> Hi Raphinesse, Thanks for the Jasmine 3 update. I m now able to build and
> install cordova-js module.
>
> @jesse, I tried the steps you mentioned to test platform and it works. But
> I m still not able to create and run mobile-spec project.While running the
> following command - "node
> cordova-mobile-spec\createmobilespec\createmobilespec.js --android
> --forceplugins", I get the following error - Error: Module cordova-js is
> not installed at all (direct or npm-linked) in cordova-lib
>
> Any thoughts on this?
>
> On Thu, Oct 25, 2018 at 11:43 PM gandhi rajan 
> wrote:
>
> > Thanks a lot for the response Jesse and Raphinesse. Will try out the
> > suggested steps and check out the merge as well. Will get back with further
> > updates if I m stuck.
> >
> > On Thursday, October 25, 2018,  wrote:
> >
> >> I already updated cordova-js to use more modern tooling some time ago in
> >> https://github.com/apache/cordova-js/pull/176.  I just had not gotten
> >> around to merging it yet. I did so just now.
> >>
> >> Jesse  schrieb am Do., 25. Okt. 2018, 10:19:
> >>
> >> > Hi Gandhi,
> >> >
> >> > There is an issue with this repo in that cordova-js uses a jasmine-node
> >> > version that depends on a non-secure version of growl.  This is not a
> >> > trivial fix as moving to the recommended jasmine-node@2.0.1 is a
> >> breaking
> >> > change.
> >> > I am not completely of the mind that updating is the right approach
> >> here,
> >> > as I think in many ways the cordova-js project is outdated, and the
> >> whole
> >> > process of generating platform specific cordova.js files needs to be
> >> > rethought.
> >> >
> >> > Personally, this does not block me ... I do the following:
> >> > ⚡ npm i
> >> > audited 684 packages in 2.085s
> >> > found 1 critical severity vulnerability
> >> >   run `npm audit fix` to fix them, or `npm audit` for details
> >> >
> >> > ⚡ npx grunt
> >> > ... succeeds
> >> >
> >> > ⚡ npx grunt compile:windows
> >> > Running "compile:windows" (compile) task
> >> > generated cordova.windows.js @ 243e7aac8cee0108927df0253118e36857ab9fc7
> >> in
> >> > 5ms
> >> > Done.
> >> >
> >> > The typical way a platform is released is to use cordova-coho.
> >> > ex. `coho prepare-platform-release-branch -r cordova-android --version
> >> > 9.9.9`
> >> > This takes care of all the tagging, building/copying of cordova.js to
> >> the
> >> > correct platform folder.
> >> >
> >> > About the mobile-spec workflow, I have not done this is a long time,
> >> this
> >> > was more important when we were breaking things a lot.  One expectation
> >> of
> >> > the tooling that may not be explicitly listed is that all repos are
> >> > expected to be cloned as peers.  cordova-coho has commands that can help
> >> > manage the multitude of repos for you.
> >> >
> >> > Not sure if this helps you move forward, I am happy to dig into this
> >> more
> >> > with you.
> >> >
> >> > Cheers,
> >> >   Jesse
> >> >
> >> > @purplecabbage
> >> > risingj.com
> >> >
> >> >
> >> > On Tue, Oct 23, 2018 at 10:22 PM gandhi rajan 
> >> > wrote:
> >> >
> >> > > Hi All,
> >> > >
> >> > > I was trying to understand the release process for Cordova platforms
> >> as
> >> > > mentioned in the following link -
> >> > >
> >> > >
> >> >
> >> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
> >> > > .
> >> > >
> >> > > While following the steps mentioned to test plugins with
> >> > > cordova-mobile-spec project, I got an error stating cordova-js module
> >> is
> >> > > not installed. When I tried to install cordova-js, the installation
> >> fails
> >> > > stating one critical severity vulnerability.On running npm audit on
> >> > > cordova-js, it states that the critical vulnerability is related to
> >> growl
> >> > > version.
> >> > >
> >> > > Can someone let me know whether I m missing some steps which is
> >> causing
> >> > > this issue or it's a vulnerability that needs to be fixed as I m not
> >> able
> >> > > to proceed with cordova-js module installation?
> >> > >
> >> > > Any help is really appreciated. Thanks in advance.
> >> > >
> >> > >
> >> > > --
> >> > > Regards,
> >> > > Gandhi
> >> > >
> >> > > "The best way to find urself is to lose urself in the service of
> >> others
> >> > > !!!"
> >> > >
> >> >
> >>
> >
> >
> > --
> > Regards,
> > Gandhi
> >
> > "The best way to find urself is to lose urself in the service of others
> > !!!"
> >
> >
>
> --
> Regards,
> Gandhi
>
> "The best way to find urself is to lose urself in the service of others !!!"

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

Re: Facing issue in testing release process of Cordova platforms

2018-10-27 Thread gandhi rajan

Hi Raphinesse, Thanks for the Jasmine 3 update. I m now able to build and
install cordova-js module.

@jesse, I tried the steps you mentioned to test platform and it works. But
I m still not able to create and run mobile-spec project.While running the
following command - "node
cordova-mobile-spec\createmobilespec\createmobilespec.js --android
--forceplugins", I get the following error - Error: Module cordova-js is
not installed at all (direct or npm-linked) in cordova-lib

Any thoughts on this?

On Thu, Oct 25, 2018 at 11:43 PM gandhi rajan 
wrote:

> Thanks a lot for the response Jesse and Raphinesse. Will try out the
> suggested steps and check out the merge as well. Will get back with further
> updates if I m stuck.
>
> On Thursday, October 25, 2018,  wrote:
>
>> I already updated cordova-js to use more modern tooling some time ago in
>> https://github.com/apache/cordova-js/pull/176.  I just had not gotten
>> around to merging it yet. I did so just now.
>>
>> Jesse  schrieb am Do., 25. Okt. 2018, 10:19:
>>
>> > Hi Gandhi,
>> >
>> > There is an issue with this repo in that cordova-js uses a jasmine-node
>> > version that depends on a non-secure version of growl.  This is not a
>> > trivial fix as moving to the recommended jasmine-node@2.0.1 is a
>> breaking
>> > change.
>> > I am not completely of the mind that updating is the right approach
>> here,
>> > as I think in many ways the cordova-js project is outdated, and the
>> whole
>> > process of generating platform specific cordova.js files needs to be
>> > rethought.
>> >
>> > Personally, this does not block me ... I do the following:
>> > ⚡ npm i
>> > audited 684 packages in 2.085s
>> > found 1 critical severity vulnerability
>> >   run `npm audit fix` to fix them, or `npm audit` for details
>> >
>> > ⚡ npx grunt
>> > ... succeeds
>> >
>> > ⚡ npx grunt compile:windows
>> > Running "compile:windows" (compile) task
>> > generated cordova.windows.js @ 243e7aac8cee0108927df0253118e36857ab9fc7
>> in
>> > 5ms
>> > Done.
>> >
>> > The typical way a platform is released is to use cordova-coho.
>> > ex. `coho prepare-platform-release-branch -r cordova-android --version
>> > 9.9.9`
>> > This takes care of all the tagging, building/copying of cordova.js to
>> the
>> > correct platform folder.
>> >
>> > About the mobile-spec workflow, I have not done this is a long time,
>> this
>> > was more important when we were breaking things a lot.  One expectation
>> of
>> > the tooling that may not be explicitly listed is that all repos are
>> > expected to be cloned as peers.  cordova-coho has commands that can help
>> > manage the multitude of repos for you.
>> >
>> > Not sure if this helps you move forward, I am happy to dig into this
>> more
>> > with you.
>> >
>> > Cheers,
>> >   Jesse
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> >
>> > On Tue, Oct 23, 2018 at 10:22 PM gandhi rajan 
>> > wrote:
>> >
>> > > Hi All,
>> > >
>> > > I was trying to understand the release process for Cordova platforms
>> as
>> > > mentioned in the following link -
>> > >
>> > >
>> >
>> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
>> > > .
>> > >
>> > > While following the steps mentioned to test plugins with
>> > > cordova-mobile-spec project, I got an error stating cordova-js module
>> is
>> > > not installed. When I tried to install cordova-js, the installation
>> fails
>> > > stating one critical severity vulnerability.On running npm audit on
>> > > cordova-js, it states that the critical vulnerability is related to
>> growl
>> > > version.
>> > >
>> > > Can someone let me know whether I m missing some steps which is
>> causing
>> > > this issue or it's a vulnerability that needs to be fixed as I m not
>> able
>> > > to proceed with cordova-js module installation?
>> > >
>> > > Any help is really appreciated. Thanks in advance.
>> > >
>> > >
>> > > --
>> > > Regards,
>> > > Gandhi
>> > >
>> > > "The best way to find urself is to lose urself in the service of
>> others
>> > > !!!"
>> > >
>> >
>>
>
>
> --
> Regards,
> Gandhi
>
> "The best way to find urself is to lose urself in the service of others
> !!!"
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Facing issue in testing release process of Cordova platforms

2018-10-25 Thread gandhi rajan

Thanks a lot for the response Jesse and Raphinesse. Will try out the
suggested steps and check out the merge as well. Will get back with further
updates if I m stuck.

On Thursday, October 25, 2018,  wrote:

> I already updated cordova-js to use more modern tooling some time ago in
> https://github.com/apache/cordova-js/pull/176.  I just had not gotten
> around to merging it yet. I did so just now.
>
> Jesse  schrieb am Do., 25. Okt. 2018, 10:19:
>
> > Hi Gandhi,
> >
> > There is an issue with this repo in that cordova-js uses a jasmine-node
> > version that depends on a non-secure version of growl.  This is not a
> > trivial fix as moving to the recommended jasmine-node@2.0.1 is a
> breaking
> > change.
> > I am not completely of the mind that updating is the right approach here,
> > as I think in many ways the cordova-js project is outdated, and the whole
> > process of generating platform specific cordova.js files needs to be
> > rethought.
> >
> > Personally, this does not block me ... I do the following:
> > ⚡ npm i
> > audited 684 packages in 2.085s
> > found 1 critical severity vulnerability
> >   run `npm audit fix` to fix them, or `npm audit` for details
> >
> > ⚡ npx grunt
> > ... succeeds
> >
> > ⚡ npx grunt compile:windows
> > Running "compile:windows" (compile) task
> > generated cordova.windows.js @ 243e7aac8cee0108927df0253118e36857ab9fc7
> in
> > 5ms
> > Done.
> >
> > The typical way a platform is released is to use cordova-coho.
> > ex. `coho prepare-platform-release-branch -r cordova-android --version
> > 9.9.9`
> > This takes care of all the tagging, building/copying of cordova.js to the
> > correct platform folder.
> >
> > About the mobile-spec workflow, I have not done this is a long time, this
> > was more important when we were breaking things a lot.  One expectation
> of
> > the tooling that may not be explicitly listed is that all repos are
> > expected to be cloned as peers.  cordova-coho has commands that can help
> > manage the multitude of repos for you.
> >
> > Not sure if this helps you move forward, I am happy to dig into this more
> > with you.
> >
> > Cheers,
> >   Jesse
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Oct 23, 2018 at 10:22 PM gandhi rajan 
> > wrote:
> >
> > > Hi All,
> > >
> > > I was trying to understand the release process for Cordova platforms as
> > > mentioned in the following link -
> > >
> > >
> > https://github.com/apache/cordova-coho/blob/master/docs/
> platforms-release-process.md
> > > .
> > >
> > > While following the steps mentioned to test plugins with
> > > cordova-mobile-spec project, I got an error stating cordova-js module
> is
> > > not installed. When I tried to install cordova-js, the installation
> fails
> > > stating one critical severity vulnerability.On running npm audit on
> > > cordova-js, it states that the critical vulnerability is related to
> growl
> > > version.
> > >
> > > Can someone let me know whether I m missing some steps which is causing
> > > this issue or it's a vulnerability that needs to be fixed as I m not
> able
> > > to proceed with cordova-js module installation?
> > >
> > > Any help is really appreciated. Thanks in advance.
> > >
> > >
> > > --
> > > Regards,
> > > Gandhi
> > >
> > > "The best way to find urself is to lose urself in the service of others
> > > !!!"
> > >
> >
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Facing issue in testing release process of Cordova platforms

2018-10-25 Thread Jesse

Nice Raphael! Thanks.


On Thu, Oct 25, 2018 at 1:30 AM  wrote:

> I already updated cordova-js to use more modern tooling some time ago in
> https://github.com/apache/cordova-js/pull/176.  I just had not gotten
> around to merging it yet. I did so just now.
>
> Jesse  schrieb am Do., 25. Okt. 2018, 10:19:
>
> > Hi Gandhi,
> >
> > There is an issue with this repo in that cordova-js uses a jasmine-node
> > version that depends on a non-secure version of growl.  This is not a
> > trivial fix as moving to the recommended jasmine-node@2.0.1 is a
> breaking
> > change.
> > I am not completely of the mind that updating is the right approach here,
> > as I think in many ways the cordova-js project is outdated, and the whole
> > process of generating platform specific cordova.js files needs to be
> > rethought.
> >
> > Personally, this does not block me ... I do the following:
> > ⚡ npm i
> > audited 684 packages in 2.085s
> > found 1 critical severity vulnerability
> >   run `npm audit fix` to fix them, or `npm audit` for details
> >
> > ⚡ npx grunt
> > ... succeeds
> >
> > ⚡ npx grunt compile:windows
> > Running "compile:windows" (compile) task
> > generated cordova.windows.js @ 243e7aac8cee0108927df0253118e36857ab9fc7
> in
> > 5ms
> > Done.
> >
> > The typical way a platform is released is to use cordova-coho.
> > ex. `coho prepare-platform-release-branch -r cordova-android --version
> > 9.9.9`
> > This takes care of all the tagging, building/copying of cordova.js to the
> > correct platform folder.
> >
> > About the mobile-spec workflow, I have not done this is a long time, this
> > was more important when we were breaking things a lot.  One expectation
> of
> > the tooling that may not be explicitly listed is that all repos are
> > expected to be cloned as peers.  cordova-coho has commands that can help
> > manage the multitude of repos for you.
> >
> > Not sure if this helps you move forward, I am happy to dig into this more
> > with you.
> >
> > Cheers,
> >   Jesse
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Oct 23, 2018 at 10:22 PM gandhi rajan 
> > wrote:
> >
> > > Hi All,
> > >
> > > I was trying to understand the release process for Cordova platforms as
> > > mentioned in the following link -
> > >
> > >
> >
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
> > > .
> > >
> > > While following the steps mentioned to test plugins with
> > > cordova-mobile-spec project, I got an error stating cordova-js module
> is
> > > not installed. When I tried to install cordova-js, the installation
> fails
> > > stating one critical severity vulnerability.On running npm audit on
> > > cordova-js, it states that the critical vulnerability is related to
> growl
> > > version.
> > >
> > > Can someone let me know whether I m missing some steps which is causing
> > > this issue or it's a vulnerability that needs to be fixed as I m not
> able
> > > to proceed with cordova-js module installation?
> > >
> > > Any help is really appreciated. Thanks in advance.
> > >
> > >
> > > --
> > > Regards,
> > > Gandhi
> > >
> > > "The best way to find urself is to lose urself in the service of others
> > > !!!"
> > >
> >
>

Re: Facing issue in testing release process of Cordova platforms

2018-10-25 Thread raphinesse

I already updated cordova-js to use more modern tooling some time ago in
https://github.com/apache/cordova-js/pull/176.  I just had not gotten
around to merging it yet. I did so just now.

Jesse  schrieb am Do., 25. Okt. 2018, 10:19:

> Hi Gandhi,
>
> There is an issue with this repo in that cordova-js uses a jasmine-node
> version that depends on a non-secure version of growl.  This is not a
> trivial fix as moving to the recommended jasmine-node@2.0.1 is a breaking
> change.
> I am not completely of the mind that updating is the right approach here,
> as I think in many ways the cordova-js project is outdated, and the whole
> process of generating platform specific cordova.js files needs to be
> rethought.
>
> Personally, this does not block me ... I do the following:
> ⚡ npm i
> audited 684 packages in 2.085s
> found 1 critical severity vulnerability
>   run `npm audit fix` to fix them, or `npm audit` for details
>
> ⚡ npx grunt
> ... succeeds
>
> ⚡ npx grunt compile:windows
> Running "compile:windows" (compile) task
> generated cordova.windows.js @ 243e7aac8cee0108927df0253118e36857ab9fc7 in
> 5ms
> Done.
>
> The typical way a platform is released is to use cordova-coho.
> ex. `coho prepare-platform-release-branch -r cordova-android --version
> 9.9.9`
> This takes care of all the tagging, building/copying of cordova.js to the
> correct platform folder.
>
> About the mobile-spec workflow, I have not done this is a long time, this
> was more important when we were breaking things a lot.  One expectation of
> the tooling that may not be explicitly listed is that all repos are
> expected to be cloned as peers.  cordova-coho has commands that can help
> manage the multitude of repos for you.
>
> Not sure if this helps you move forward, I am happy to dig into this more
> with you.
>
> Cheers,
>   Jesse
>
> @purplecabbage
> risingj.com
>
>
> On Tue, Oct 23, 2018 at 10:22 PM gandhi rajan 
> wrote:
>
> > Hi All,
> >
> > I was trying to understand the release process for Cordova platforms as
> > mentioned in the following link -
> >
> >
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
> > .
> >
> > While following the steps mentioned to test plugins with
> > cordova-mobile-spec project, I got an error stating cordova-js module is
> > not installed. When I tried to install cordova-js, the installation fails
> > stating one critical severity vulnerability.On running npm audit on
> > cordova-js, it states that the critical vulnerability is related to growl
> > version.
> >
> > Can someone let me know whether I m missing some steps which is causing
> > this issue or it's a vulnerability that needs to be fixed as I m not able
> > to proceed with cordova-js module installation?
> >
> > Any help is really appreciated. Thanks in advance.
> >
> >
> > --
> > Regards,
> > Gandhi
> >
> > "The best way to find urself is to lose urself in the service of others
> > !!!"
> >
>

Re: Facing issue in testing release process of Cordova platforms

2018-10-25 Thread Jesse

Hi Gandhi,

There is an issue with this repo in that cordova-js uses a jasmine-node
version that depends on a non-secure version of growl.  This is not a
trivial fix as moving to the recommended jasmine-node@2.0.1 is a breaking
change.
I am not completely of the mind that updating is the right approach here,
as I think in many ways the cordova-js project is outdated, and the whole
process of generating platform specific cordova.js files needs to be
rethought.

Personally, this does not block me ... I do the following:
⚡ npm i
audited 684 packages in 2.085s
found 1 critical severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details

⚡ npx grunt
... succeeds

⚡ npx grunt compile:windows
Running "compile:windows" (compile) task
generated cordova.windows.js @ 243e7aac8cee0108927df0253118e36857ab9fc7 in
5ms
Done.

The typical way a platform is released is to use cordova-coho.
ex. `coho prepare-platform-release-branch -r cordova-android --version
9.9.9`
This takes care of all the tagging, building/copying of cordova.js to the
correct platform folder.

About the mobile-spec workflow, I have not done this is a long time, this
was more important when we were breaking things a lot.  One expectation of
the tooling that may not be explicitly listed is that all repos are
expected to be cloned as peers.  cordova-coho has commands that can help
manage the multitude of repos for you.

Not sure if this helps you move forward, I am happy to dig into this more
with you.

Cheers,
  Jesse

@purplecabbage
risingj.com

On Tue, Oct 23, 2018 at 10:22 PM gandhi rajan 
wrote:

> Hi All,
>
> I was trying to understand the release process for Cordova platforms as
> mentioned in the following link -
>
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
> .
>
> While following the steps mentioned to test plugins with
> cordova-mobile-spec project, I got an error stating cordova-js module is
> not installed. When I tried to install cordova-js, the installation fails
> stating one critical severity vulnerability.On running npm audit on
> cordova-js, it states that the critical vulnerability is related to growl
> version.
>
> Can someone let me know whether I m missing some steps which is causing
> this issue or it's a vulnerability that needs to be fixed as I m not able
> to proceed with cordova-js module installation?
>
> Any help is really appreciated. Thanks in advance.
>
>
> --
> Regards,
> Gandhi
>
> "The best way to find urself is to lose urself in the service of others
> !!!"
>

Facing issue in testing release process of Cordova platforms

2018-10-23 Thread gandhi rajan

Hi All,

I was trying to understand the release process for Cordova platforms as
mentioned in the following link -
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
.

While following the steps mentioned to test plugins with
cordova-mobile-spec project, I got an error stating cordova-js module is
not installed. When I tried to install cordova-js, the installation fails
stating one critical severity vulnerability.On running npm audit on
cordova-js, it states that the critical vulnerability is related to growl
version.

Can someone let me know whether I m missing some steps which is causing
this issue or it's a vulnerability that needs to be fixed as I m not able
to proceed with cordova-js module installation?

Any help is really appreciated. Thanks in advance.


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Facing issue in testing release process of Cordova platforms

Re: Facing issue in testing release process of Cordova platforms

Re: Facing issue in testing release process of Cordova platforms

Re: Facing issue in testing release process of Cordova platforms

Re: Facing issue in testing release process of Cordova platforms

Re: Facing issue in testing release process of Cordova platforms

Re: Facing issue in testing release process of Cordova platforms

Re: Facing issue in testing release process of Cordova platforms

Re: Facing issue in testing release process of Cordova platforms

Facing issue in testing release process of Cordova platforms

10 matches

Site Navigation

Mail list logo

Footer information