This relates solely to instructions on how to *build* the site, and not the
contents of the site itself.
Bringing this up here for discussion since a committer wants to revert a
change by another committer, and there is potential for disagreement.
The pull request to revert is here:
https://githu
Thanks to Tommy, one of Cordova's committers, for this!
https://github.com/apache/cordova-docs/pull/728
This removes our only use of React, in plugins.cordova.io
This removal is required by Apache Legal:
https://issues.apache.org/jira/browse/CB-13025
I am actually surprised deploying is a manual process at all.
Having read the steps, I understand why of course.
As a person that jumps in on all kinds of projects, I absolutely
prefer docs that list each and every little step needed (including all
the `cd` etc).
The need for manual steps or chec
Github user janpio commented on the issue:
https://github.com/apache/cordova-plugin-console/pull/25
Nice.
Does this mean that the 2.0.0 of the console plugin can be installed on
`cordova-ios` 4.5.0 without causing the build problems?
---
---
Github user artyom-dorokhov commented on the issue:
https://github.com/apache/cordova-plugin-inappbrowser/pull/210
i'd love to have it merged. current version of inappbrowser with its
styling looks like from 90's
---
--
Github user timbru31 commented on the issue:
https://github.com/apache/cordova-plugin-inappbrowser/pull/210
@artyom-dorokhov you might want to check out
https://github.com/EddyVerbruggen/cordova-plugin-safariviewcontroller
---
Github user artyom-dorokhov commented on the issue:
https://github.com/apache/cordova-plugin-inappbrowser/pull/210
@timbru31 thanks for the tip, but inappbrowser can inject js/css on a
third-party page and it's the main point of using it.
---
Yes, ideally our deployment process should be automated. Also, it should *not*
be an SVN commit. It should be an rsync or an scp command. I would support any
initiatives to move to either one of those. If we had automated deployment,
this discussion would be moot.
How much would it cost us to j
We have an issue posted to make docs publishing automatic:
https://issues.apache.org/jira/browse/CB-13162
Not to derail the topic, but there is a longer wishlist in that issue,
and I do think achieving the goals in that issue would require
reworking the docs repository quite a bit. We can discuss
Github user stevengill commented on the issue:
https://github.com/apache/cordova-docs/pull/729
LGTM.
I personally prefer `npm run serve` over `node_modules/.bin/gulp build
--prod` but can deal with it.
---
---
PR looks fine to me. Keep the svn commit stuff. Lets merge and move on
On Wed, Sep 13, 2017 at 10:08 AM, Filip Maj wrote:
> We have an issue posted to make docs publishing automatic:
> https://issues.apache.org/jira/browse/CB-13162
>
> Not to derail the topic, but there is a longer wishlist in t
@fil: why is reworking the docs repo needed for automatic deployment?
@steve: could you merge it then? I'm far too rusty on my Cordova-ing to
remember how to set up my remotes to push to the ASF repo, sorry. :(
Kindly,
Dmitry
> On Sep 13, 2017, at 1:08 PM, Filip Maj wrote:
>
> We have an issu
To be clear, we don't need to redesign anything to automate docs
deployment. It is in the realm of possibility to simply automate what
we have today. I just feel like what we have today is a design where
translations are an afterthought, which I think is a bad tradeoff,
especially given the popular
So, translations were always a semi-manual process. In that sense, they're as
much an "afterthought" as they ever were. However the current design permits
automation of translation within its build process pretty cleanly. It's just a
matter of implementing it. It's not trivial, but it's about as
Looks like the redirect didn't work since the move to Github Apache Org for
cordova-status, fixed.
3 components have build failures:
1. cordova-paramedic (Travis fail, AppVeyor fail)
2. cordova-fetch (Travis pass, AppVeyor fail)
3. cordova-android (Travis - something wrong with the bui
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-docs/pull/729
---
-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
Nightly build #484 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/484/consoleFull
-
Jenkins for Apache Cordova
-
17 matches
Mail list logo
