This is an automated email from the ASF dual-hosted git repository.
rombert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new 84ab113 Update building instructions in case the automatic publish
fails.
84ab113 is described below
commit 84ab113556587c88cb42c55368f401cbbba2568d
Author: Robert Munteanu <[email protected]>
AuthorDate: Tue Feb 6 15:25:38 2018 +0200
Update building instructions in case the automatic publish fails.
---
README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/README.md b/README.md
index 218f220..dac4b9c 100644
--- a/README.md
+++ b/README.md
@@ -22,6 +22,8 @@ The [ASF's gitpubsub
mechanism](https://blogs.apache.org/infra/entry/git_based_w
We could automate this using a Jenkins job that's restricted to run on build
nodes having the `git-websites` label, as done by [Apache
PLC4X](http://plc4x.incubator.apache.org/developers/website.html).
+Note that the publish-scm goal might fail if you add lots of changes due to
[MSCMPUB-18](https://issues.apache.org/jira/browse/MSCMPUB-18). In that
scenario you have to manually perform the git operations, see for instance
[this file at revision
3e58fbd7](https://github.com/apache/sling-site/blob/3e58fbd768344d90185a2123ca30afb6ec4f9000/README.md).
+
## Variables in page content
Adding `expandVariables=true` to a page's front matter enables simple
variables replacement, see the `pageVariables` map in
templates code for which variables are supported or to add more variables. A
pattern like `${sling_tagline}` in page content
--
To stop receiving notification emails like this one, please contact
[email protected].
