I prefer 2 to not pollute the Sling Site Git repo with generated artifacts. But even with 2 we should have an according Jenkins Job which executes this Maven Build & Deploy automatically.
> On 2. Oct 2017, at 21:33, Robert Munteanu <romb...@apache.org> wrote: > > Hi, > > I think we can simplify the site publishing setup and it should be > enough to work only on the master branch. > > I see two possible options: > > 1) Set up a Jenkins job to rebuild the site and push automatically . > This _should_ be possible based on [1] > > 2) Configure the maven-scm-publish-plugin to publish changes. This is > done for instance for Oak [2] > > Preferences? > > Thanks, > > Robert > > [1]: https://issues.apache.org/jira/browse/INFRA-12425 > [2]: https://github.com/apache/jackrabbit-oak/blob/fbc23b57f24576352cc2 > 04a52b90d852d2be7a6a/oak-doc/pom.xml#L46-L80
