GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2033
[FLINK-3887] improve dependency management for building docs
The Flink documentation build process is currently quite messy. These
changes move us to a new build process with proper dependency handling. It
assures that we all use the same dependency versions for consistent build
output. Also, it eases the automated building process on other systems (like
the ASF Buildbot). The goal was to make the documentation build process easier
and self-contained.
I would like to merge these changes to all `release-x.x` branches because
it avoids to have special per-release documentation build rules.
- use Ruby's Bundler Gem to install dependencies
- update README
- adapt Dockerfile
- add additional rules to .gitignore
- change default doc output path from /target to /content (default path of
the flink-web repository)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink FLINK-3887
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2033.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2033
----
commit 929d75b3dfaf8e55fb1af47e4fdeecd9101855ed
Author: Maximilian Michels <[email protected]>
Date: 2016-05-12T13:02:59Z
[FLINK-3887] improve dependency management for building docs
The Flink documentation build process is currently quite messy. These
changes move us to a new build process with proper dependency
handling. It assures that we all use the same dependency versions for
consistent build output. Also, it eases the automated building process
on other systems (like the ASF Buildbot). The goal was to make the
documentation build process easier and self-contained.
- use Ruby's Bundler Gem to install dependencies
- update README
- adapt Dockerfile
- add additional rules to .gitignore
- change default doc output path from /target to /content
(default path of the flink-web repository)
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
