[
https://issues.apache.org/jira/browse/CB-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294243#comment-14294243
]
ASF GitHub Bot commented on CB-8307:
------------------------------------
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-windows/pull/55#issuecomment-71734265
This may be better served living in cordova-coho which is the tool that we
use to package a release.
Or possibly have the generate_certificate.js call `npm install node-forge`
so only people who call `npm generatekey` will ever need it.
I am not completely sure what the impact is of having node-forge as a
dependency, it may not be that big of a deal, but we will be looking at some
point to remove npm_modules folder and have platform installs actually use npm
install directly. ie No bundling of the dependencies.
Not sure what is the best approach here.
> cordova-windows cert expires in 2015
> ------------------------------------
>
> Key: CB-8307
> URL: https://issues.apache.org/jira/browse/CB-8307
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
> Affects Versions: 3.5.0, 4.1.3
> Reporter: Kirk Shoop
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> There is a pfx file checked into the project template that is used to deploy
> the appx to a device when debugging.
> The pfx file contains a certificate that will expire one year after it was
> created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
