Nightly build #897 for cordova has succeeded!

[Apache Jenkins Server]

Nightly build #897 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g 
cordova@nightly'

For details check build console at 
https://builds.apache.org/job/cordova-nightly/897/consoleFull

-
Jenkins for Apache Cordova

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

Re: [proposal] Remove tool generated docs from camera plugin?

[julio cesar sanchez]

Thanks for the opinions, sent a PR
https://github.com/apache/cordova-plugin-camera/pull/365

El mié., 31 oct. 2018 a las 1:48, Gearóid M () escribió:

> +1 for simplicity and consistency with other readme files
>
> On Wed, 31 Oct 2018, at 09:40, Jesse wrote:
> > +1 to a hand written readme!
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Oct 30, 2018 at 5:18 PM julio cesar sanchez <
> jcesarmob...@gmail.com>
> > wrote:
> >
> > > Bumping this old thread again as I accidentally "undid" some manual
> changes
> > > Jan did on cordova-plugin-camera README.
> > >
> > > Part of the cordova-plugin-camera README is generated from here
> > >
> > >
> https://github.com/daserge/dmd-plugin-cordova-plugin/blob/master/partial/cdv-header.hbs
> > > and some other files on that repo. So I think we should remove that
> > > dependency and switch to a regular README without automatic generation
> as
> > > it's the only plugin doing that.
> > >
> > > Thoughts?
> > >
> > >
> > >
> > > El mié., 18 oct. 2017 a las 0:52, Steven Gill ( >)
> > > escribió:
> > >
> > > > I'm fine with going back to a simple readme
> > > >
> > > > On Sun, Oct 15, 2017 at 12:52 AM, julio cesar sanchez <
> > > > jcesarmob...@gmail.com> wrote:
> > > >
> > > > > The README.md already have a section
> > > > >  > > > > documentation-is-generated-by-a-tool>
> > > > > about how the README.md is generated. But maybe it should be more
> clear
> > > > and
> > > > > say that the README.md shouldn't be updated manually.
> > > > >
> > > > > BTW, I sent a PR <
> > > > https://github.com/apache/cordova-plugin-camera/pull/291
> > > > > >
> > > > > to make the template be in sync with the README.md changes. If
> anybody
> > > > can
> > > > > take a look it would be good. Not sure if I can merge while the
> tests
> > > are
> > > > > failing, but I only changed the template, so I'm pretty sure I
> didn't
> > > > break
> > > > > anything and tests are failing in all other plugins, but that's
> another
> > > > > topic.
> > > > >
> > > > > About if it's a good idea, I've found the original cordova-discuss
> > > issue
> > > > >  and proposal
> > > > >  and reading
> them I
> > > > > think it's a good idea as I understand that the API part of the
> docs
> > > are
> > > > > automatically generated from the js files, which avoids them to be
> out
> > > of
> > > > > sync if a js change is made.
> > > > >
> > > > >
> > > > > 2017-10-15 1:07 GMT+02:00 Jan Piotrowski :
> > > > >
> > > > > > The "not aware" problem can probably be resolved (80/20) by
> adding
> > > > > > comments to the template that are also in the generated output.
> > > > > >
> > > > > > But it the TEMPLATE.md actually a good idea? Is it worth the
> extra
> > > > > effort?
> > > > > >
> > > > > > -J
> > > > > >
> > > > > > 2017-10-15 0:01 GMT+02:00 julio cesar sanchez <
> > > jcesarmob...@gmail.com
> > > > >:
> > > > > > > cordova-plugin-camera docs work on a different way than other
> > > > plugins.
> > > > > > The
> > > > > > > README.md is generated from jsdoc2md/TEMPLATE.md when the
> commit is
> > > > > done.
> > > > > > > I think it was a proof of concept to be done in all the
> plugins,
> > > but
> > > > it
> > > > > > the
> > > > > > > end it was only done in camera plugin.
> > > > > > > The problem is most people is not aware of this, so they just
> > > update
> > > > > the
> > > > > > > README.md manually as on any other plugins, and most of the
> > > > committers
> > > > > > > aren't aware neither or forgot about it and just merge those
> > > changes.
> > > > > > >
> > > > > > > So, I was about to send a new PR and the jsdoc2md/TEMPLATE.md
> is
> > > out
> > > > of
> > > > > > > sync with the README.md.
> > > > > > >
> > > > > > > So, we have two options, we can move back to a regular
> README.md
> > > like
> > > > > the
> > > > > > > other plugins, or do this in all the plugins and not accept
> > > README.md
> > > > > > file
> > > > > > > changes without the corresponding jsdoc2md/TEMPLATE.md.
> > > > > > >
> > > > > > > What do you think?
> > > > > >
> > > > > >
> -
> > > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
>
> -
> 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

[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: plugins release?

[Jan Piotrowski]

Julio, I would be happy to pair with you on some plugin releases.

As you already noticed, the release processes via coho need some
serious work now that we are on GitHub issues instead of JIRA, so we
have some additional work ahead of us.

First step would be to identify which plugin to start with.
(I suggest selecting just 1 and seeing that through, then continue
with more if/when we are successful).

@Oliver: What you wrote mainly applies to the platforms - the plugin
release process should be independent from that. But we will keep that
in mind of course.

J

Am Di., 16. Okt. 2018 um 13:34 Uhr schrieb Oliver Salzburg
:
>
> I believe the issue with the pending releases is not that nobody is
> performing the release task. There are still implementation details
> being worked on if I'm not mistaken.
>
> The next release will supposedly introduce several major breaking
> changes, which have to be prepared for thoroughly.
>
> On 2018-10-13 22:02, julio cesar sanchez wrote:
> > Today I was checking github issues and noticed that a lot of them were
> > supposedly fixed already, but people are reporting them again as we have
> > not done a release since April and they are using the latest release and
> > not master.
> >
> > So, is anybody willing to do a release? If not I can try, but last time I
> > tried I wasn't able to finish it because of some problem with coho.
> >
> > Also, related to coho, it supposedly creates a JIRA issue, but that's not
> > possible anymore, so should we manually create a release issue per plugin?
> > Or patch coho to automatically create them? (if possible).
> > How are you doing it since we switched to github issues? (cc Chris as I
> > think you did most/all releases since then)
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

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

Nightly build #896 for cordova has succeeded!

[Apache Jenkins Server]

Nightly build #896 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g 
cordova@nightly'

For details check build console at 
https://builds.apache.org/job/cordova-nightly/896/consoleFull

-
Jenkins for Apache Cordova

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